man, @officialmcafee would’ve been so psyched for the entire world finally latching onto PHP (until he would discover they are talking about some nerd shit and not grade-a alpha-pyrrolidinohexanophenone)
OpenAI independently reported the same root cause ON THE SAME DAY?
I hope that it is just a coincidence...
anthropic has employees installing mics in their own offices.. openAI had some questionable situation with the navier stokes discovery. we need to stop sending them good context..
.. although most collisions are probably just people rolling the virtual dice in a similar way ;)
github.com/blasty/php-8.5.4-… i accidentally marked this repo as public i dont know if its ANY GOOD. bbiab
had some time to kill en route to #TheSAS2026 dinner party.. so clanked on php apocalypse PoC.. ;-PPpppPp
blasty retweeted
All the details including the slides are now available at quentinkaiser.be/security/20…
printer vendors love it when you crack their toner DRM and start selling counterfeit cartridges/refills
Finally our HP printer will accept 3rd party ink! Thanx @morluto
github.com/morluto/rea
so what's the proper mitigation for a ledger style hw supplychain attack? tiny LCD screens with encrypted SPI bus ? :-P
you cannot *really* defend against any of this, of course. while this is a pretty obvious bug and not some bloomberg-rice-grain-sized-implant; expecting endusers to take apart their devices and visually inspect the PCBs is about as bad as UX can get. but more importantly it could also provide a false sense of security. what if there's a less obvious implant? some backdoored uC/secure element ICs, would you be able to spot them?! 👻














