A bit of a rant, but since it looks like people are still trying to consider all those technologies are equivalent... I think it's good to have an explanation on what makes containers different.

Personal backups don't have to be fancy... And probably shouldn't.

This is clearly needed. This should increase the maturity of the security practice around Fediverse software.

The "asleep at the wheel" effect is real with such tools. The consequences can be dire in quite a few fields. Here is a good illustration with OSINT.

This is considered standard practice at this point. The article does a good job explaining it and the reasoning behind it.

It's better if you prepare your security policies properly...

And yet another reverse proxy to use as a scraper deterrent... It looks like several are popping every week lately.

When a big player has to prepare a labyrinth of AI generated content to trap bots used to feed generative AI learning pipelines... something feels wrong.

Fascinating exploration of the techniques scammers are using to hook their victims

Nice exploration of the microcode patching flaw which was disclosed recently. This gives a glimpse at the high level of complexity the x86 family brings on the table.

Another example that on such ecosystems you're not really owning your device. Seek alternatives!

We're indeed close to universal HTTPS adoption. One last push please?

That's a lot of stalkerware in the wild. And this exploit is only about two such apps. What's wrong with people that they install this kind of crap on their loved ones smarphones?

The security implications of using LLMs are real. With the high complexity and low explainability of such models it opens the door to hiding attacks in plain sight.

This is a worthy questioning... We try to reuse, but maybe we do it too much? For sure some ecosystems quickly lead to hundreds of dependencies even for small features.

The browser extension ecosystems are definitely a weak link in term of security. Better not have too many random extensions installed.

Let's hope security teams don't get saturated with low quality security reports like this...

Interesting approach to have secure and decentralized naming while keeping it human readable.

Will we see more deployments of C++ standard library with bound checking by default? It definitely looks tempting.

Seeing the amount of PHP code open on the internet, it's indeed important to harden the runtime (at long last).