Subverb

Anyone who uses this should be considering switching to Linux though.

I was just reminding you that many of us have jobs or software tools that preclude us from using Linux day-to-day regardless of how much we might like the idea. Having a more comfortable windows experience has value to us.

I’m locked on windows because of very expensive embedded systems dev tools. Give people some credit for having considered linux; not everyone can switch.

I’d love to switch to linux but it just doesn’t make sense for me.

I’m an embedded systems developer and my proprietary toolchain is windows only. Additionally I use several Adobe product routinely (illustrator, photoshop, premier).

Sucks.

Every kernel update (and there are tons) requires me to rebuild my third party modules, but you need to do it in a toolbox and the kernel headers version must match the running kernel version, which is actually more annoying than it sounds.

Boy, I doubt that.

My Windows 11 machine doesn’t require any of that.

Having a language dependent on indentation is absurd on the face of it. It’s a ridiculous idea that should have been ridiculed from the outset.

Brexit was such a monumental mistake. Worse than the US electing Trump once, but probably not worse than electing Trump twice.

The malicious code was written and debugged at their convenience and saved as an object module linker file that had been stripped of debugger symbols (this is one of its features that made Fruend suspicious enough to keep digging when he profiled his backdoored ssh looking for that 500ms delay: there were no symbols to attribute the cpu cycles to).

It was then further obfuscated by being chopped up and placed into a pure binary file that was ostensibly included in the tarballs for the xz library build process to use as a test case file during its build process. The file was supposedly an example of a bad compressed file.

This “test” file was placed in the .gitignore seen in the repo so the file’s abscense on github was explained. Being included as a binary test file only in the tarballs means that the malicious code isn’t on github in any form. Its nowhere to be seen until you get the tarball.

The build process then creates some highly obfuscated bash scripts on the fly during compilation that check for the existence of the files (since they won’t be there if you’re building from github). If they’re there, the scripts reassemble the object module, basically replacing the code that you would see in the repo.

Thats a simplified version of why there’s no code to see, and that’s just one aspect of this thing. It’s sneaky.