The “tank” has an immobile or mostly immobile turret, depending on the particular design of this piece of battlefield ingenuity. Units appear to be making these modifications at the frontline to improve survivability against FPV drones but there isn’t a standard package.

Look at that, an OP who is just a prick.

Why? If you say to limit the spread of bacteria we have some studies that suggest it makes no difference at all

What a hot take. I bet you’re real fun at parties.

Pay them for a public ipv4.

It’s pretty uncommon. I’ve been using prerelease KDE for quite a while and rarely see any issues.

If it’s any consolation, Plasma 6 will recover from crashes like that.

Contrast that with CLI where if you forgot or don’t know any command there is little help or indicator of what’s available and what can be done without external help.

man would like to have words with your strawman.

No, this is egregious, even for Dan. Don’t feel bad. I called him out on the forums/article comments.

I’m looking at bringing Dillo back into Gentoo atm. I had to read 15k lines of code, and that’s just what’s different since the last release…

I’m a huge proponent of Gentoo Linux as a learning experience. It’s a great way to learn how the components of a system work together and the distro enables an amazing amount of configurability for your system.

Even following a handbook install in a VM can be a good experience if you’re interested.

I once spent a month automating the production of repositories for each kernel version supported on our HPC and rested every step exhaustively in isolation.

When I was satisfied I ran it with root permissions and hosed the VMs it was running on because a recursive chmod evaluated to /.

Oops.

Pipewire is great .

Write out syslogs to disk or better yet mirror to grayling or something, there might be valuable information right before the reboot.

I’ve also had weirdness where the CPU/iGPU was just faulty and the IME would halt the system. That took weeks to diagnose.

Definitely reach out to support!

It should work with ‘host’ match detection. If it isn’t working check your URIs.

Or do the sane thing and run everything on a different DNS and share 80/443.

What? Bitwarden doesn’t give a shit about non standard ports on services you’re accessing. They’re a valid part of the URI string.

Try changing your match detection settings in the add-on.

If you’re talking about bitwarden not supporting being run from container on a non standard port, we’ll, you’re doing it wrong. Expose whatever port on the container then Add a proper reverse proxy / edge router like traefik, then set up some DNS and Let’s encrypt and only use 80 and 443 for all of your services.

TL;DR don’t worry (for now) - it only impacts rpm and deb builds and impacted releases only really made it into OpenSuSe tumbleweed - if you’re running bleeding edge maybe you need to worry a little.

A laymans explanation about what happens is that the malicious package uses an indirect linkage (via systemd) to openssh and overrides a crypto function which either:

• allows access to the system to a particular key
• allows remote code execution with a particular key

Or both!

I have secondhand info that privately the reverse engineering is more advanced, but nobody wants to lead with bad info.

As for what you should do? Unless you’re running an rpm or deb based distro and you have version 5.6.0 or 5.6.1 of xz-utils installed, not much. If you are, well, that comes down to your threat model and paranoia level: either upgrade (downgrade) the package to a non-vulnerable version or dust off and nuke the site from orbit; it’s the only way to be sure.

there is no good answer

There is clearly a worst option.

I use Traefik for all of my containerised services. It’s fantastic.

At least weekly.

This link might be useful in quickly getting a binhost configured while following a standard handbook install.

https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart