B-TR3E

Usually the common vulnerability is a combination of Outlook and Active Directory. Outlook will happily execute whatever users click upon and AD lets them steal their credentials, to simplify things.

You’re welcome. It was a pleasure to set someomes ideas about Mr Gates right.

Encryption alone won’t prevent ransomware to encrypt it again. The original files need to be readable after all, so they are either unencrypted at boot or appear unencrypted to the (infected) client by machine/session key management. Nevertheless, adding an addittional, "“hostile” encryption layer will make them unreadable. The reasonable thing would be not to use a monocultural, standard setup that is known to be vulnerable to that kind of attack and first of all to get rid of fucking Outlook which has always been a dumpster fire.

Wikipedia for a beginning: https://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML I remember The Register having a more detailed (and pretty snarky) article about it back then, but I didn’t search for it yet.

Let me assure you that the original board that was voting for Open Office’s proposal was absolutely pissed off, short of dissolving but eventually unable to revert the decision because of it’s formal correctness.

…and bribed the represenatives of the “new” IETF members as well as their governments to vote for Microsoft’s standard. The latter was, of course, a matter strictly between “business partners” and probably barred behind NDAs, so “legal” as long as nobody would blow the wistle.

Ransomware attack are successful mostly against MS Active Directory and Ourlook based setups.

There are some people who míght learn from a ransomware attack. Only if it personally hits them, of course.

“bribed” is a gross simplifiction of the almost hilariously evil plot they pulled to get OOXML certified. They actually bribed a couple of smaller nation states to become IETF members and vote for Microsoft’s standard. It was a major scandal back in the day but formally legal.

Say hello to Mr Killfile…

That’s the best thing bluetooth audio can do for you. Much better than anything it does to music.

You’re an idiot who doesn’t know what you’re talking about. Pipewire isn’t really up for production (and by far not a decade old) and whoever decided to activate it by default might have had easy desktop use and switching to BT or mobile audio trash in mind. If it comes to latency, low complexity or reliability, pipewire is terrible. It also doesn’t add anything useful that jack could not do, it only adds complexity where it’s not needed.
PW is nice, if you’re a newbie and want all your crappy BT shit to connect from the desktop so you can watch five tik-tok vids at the same time using you shiny “soundbar” (and have your voice comm blasting the neighbourhood), but it’s a mess if you want to use realtime audio with more than two ports, MIDI and a device chain for recording or playback.

Don’t matter replying, “Qwel”, I put you in my special place for trolling, abusive children who do not contibute to civilization - the killfile.

I’ve been using “Linux audio”, namely jack, Ardour, freewheeling, hydrogen e.a. for more than a decade. But you can take your shiny pipewire and shove it where the sun doesn’t shine.

This sound so horrible, I might finally “upgrade” to 11.

Even by Trump’s standards it seems quite unhinged, indeed. Sounds bat shit crazy, tbh.

HN = Hacker News in this context, just in case anyone else wonders.

Yes. 300 second places, who cares? Maybe there’s an aftermarket for data Google already has stolen. Might be that Google’s prices are too high for resellers.

You mean all three apps that support waylamd are working? Wow. At the same time?

As if this hadn’t been obvious the very moment they started connecting their massive amount of same model cameras to servers under their own regime (aka " the cloud"). And as if nobody told you so.

Behold the miracle of the slipping clutch, millenials. See It working without being digital and all without an app by the ancient secrets of mechanics!