Here’s another. You being you isn’t a line of defence if someone decides to murder you on a date.

Serious answer then: you won’t be fired for being yourself.

When I had this conversation with a trans mate (who had a fucking awful Daily Heil-reading co-worker with no notion of what was appropriate conversation for the workplace) I said, “hang on a moment, isn’t [being fired over being out] illegal?” He said, “yes, but it doesn’t stop it happening.”

I believed him - he was living it, he had the experience. Conversations with him involved me getting smacked in the face with my own privilege on a regular basis. You have it easy.

Ken Livingston (back when he was mayor) famously referred to the US Ambassador as a “chiselling little crook” for the continued nonpayment of fines (I think it was in the millions even then).

Once the water companies were privatised, they took out massive loans and performed no maintenance. The loans were purely to pay shareholder dividends. Now they’re loaded down with debt.

Atop this, that crumbling infrastructure can’t handle the increased water flow that’s due to rainfall increases. So there’s been a general trend of dumping raw sewage into rivers (the fines are cheaper op ex than the capex needed to fix the situation).

It’s parasitic capitalism at its finest.

Fab, cheers.

Dare I ask what the adjective “hella” means in this context?

The issue with this is the same as with the mayoral system. The next tine the Tories get a turn, they replace it with FPTP and claim it’s “more democratic”.

The test case purported to be bad data, which you presumably want to test the correct behaviour of your dearchiver against.

Nothing this did looks to involve memory safety. It uses features like ifunc to hook behaviour.

The notion of reproducible CI is interesting, but there’s nothing preventing this setup from repeatedly producing the same output in (say) a debian package build environment.

There are many signatures here that look “obvious” with hindsight, but ultimately this comes down to establishing trust. Technical sophistication aside, this was a very successful attack against that teust foundation.

It’s definitely the case that the stack of C tooling for builds (CMakeLists.txt, autotools) makes obfuscating content easier. You might point at modern build tooling like cargo as an alternative - however, build.rs and proc macros are not typically sandboxed at present. I think it’d be possible to replicate the effects of this attack using that tooling.