Sorry if it sounded like my rant was directed at you as it absolutely wasn’t. Your comment triggered me, because I absolutely fully agreed with yours as well. ;)

setenforce 0 is much cleaner, I have found.

Its just complex

When a security mechanism becomes more complex to manage than what it is supposed to protect, it becomes a vulnerability itself.

If you had a minimal system that you built from the ground up yourself and wanted to only have that system function in very specific ways, SELinux would be perfect. I would go so far as to say it would be nearing perfection in some ways.

Sorry, but in the real world, ain’t nobody got time for that shit. If you use auto configuration tools or pre-canned configs for SELinux on a system you are unfamiliar with, it’s more likely to cause application issues, create security gaps and will likely be shut off by a Jr. admin who really has no fucking clue what he is doing anyway.

It’s just easier to keep your system patched and ensure basic network security practices anyway.

It’s not impossible to manage these days. In the early days it was, but most everything is automagic now. If I am not mistaken, SELinux can be enabled to ‘log only’ which would give you data better handled by a HIPS anyway. (Don’t quote me on that.)

To add on, it supports up to 20.1.10 and that is where the protocol may shine. However, full spacial sound is not new, and Atmos is just Sony’s proprietary version.

I stole the “sound stick” bit from Benn Jordans blunt overview on atmos: https://youtu.be/5Dw3aKbw5Wo

(Atmos is all caps as well? Meh, whatever.)

I wonder what their answer is going to be for Dolby Atmos? I am sure they could think of a another protocol that is just as pointless for your standard TV sound sticks.

Build a live boot USB for windows: https://monovm.com/blog/how-to-create-a-windows-live-usb/

There is a chance that the exe is just a wrapper for a compressed archive that contains the app to flash the bios and also the image. If the bios actually supports flashing manually, that would be super convenient.

De-escalation is easy: Russia can get the fuck out of Ukraine. All of it.

Ok, I admit I don’t understand the humor. My immediate response was, “sounds about right because of how these things happen”.(I can be kinda dumb like that sometimes.)

Security advisories may not be immediately announced until a patch is available. If this is in regards to FreeBSD-SA-24:08.openssh, a patch was available the day before it was announced and then refined for prod over the next few days : https://www.freebsd.org/security/advisories/FreeBSD-SA-24:08.openssh.asc

The timing of this stuff is always wonky and it doesn’t look like it hit a could of news places today, about a week after: https://cyberpress.org/vulnerability-in-openssh-freebsd/

I don’t get it. The key still gets declared, but it’s value is null. “name” in an empty object would return undefined, not null, correct?

(Yes, this joke whooshed, but I am curious now.)

Yeah, I would think memory as well due to the screen artifacts in that low res mode. (That depends on how x86 memory is mapped these days, I suppose.)

Cool. Now go post this in the community where they are re-writting Lemmy in Java.