Michał Purzyński retweeted
If we're rewriting football history now, I have a small suggestion:
I'd like FIFA to rescind the yellow card shown to Michael Ballack in the 2002 World Cup semifinal, the one that ruled him out of the final.
And while we're at it, we might as well replay the final against Brazil.
Michał Purzyński retweeted
💥🕵️♂️ „Sondereinsatz TRIO“ - Drei Mal kam Leonid Breschnew in die Bundesrepublik. Historische Akten zeigen nun erstmals: Der #BND bespitzelte den Sowjetführer und seine Begleiter bei den Staatsbesuchen.
ojihad.wordpress.com/2026/07…
#Geheimdienste #Geschichte #Spionage #History
Michał Purzyński retweeted
Kunal Shah nowym szefem WhatsAppa. To zobaczmy, jakie ma podejście do prywatności użytkowników :) (via Matthew Green).
Michał Purzyński retweeted
Irańska drużyna tym teledyskiem uczciła pamięć 168 dzieci zabitych przez USA w szkole w Minab
Hacking Google with A.I. for $500,000
brutecat.com/r/hacking-googl…
Michał Purzyński retweeted
New: Google is quietly trying to buy code from Android developers to train an AI coding tool as part of a "confidential" program. Tells them it's a "once-in-a-generation opportunity" for "helping society at large"
404media.co/google-is-quietl…
Michał Purzyński retweeted
Blog post: "The French have the Quantum Circuits" algassert.com/post/2602
André Schrottenloher just published a preprint showing how to construct quantum ECDLP circuits with costs similar to the ones in our zero knowledge proofs.
Michał Purzyński retweeted
Recent Linux kernel exploits, attack surface reduction, example IPSEC openwall.com/lists/oss-secur…
Discussion thread started by @hanno. Mentions approaches and old and new tools to limit (auto-)loading of kernel modules.
Michał Purzyński retweeted
Full LPE chain for the FreeBSD 14.x kernel via a setcred(2) stack buffer overflow. SMAP and SMEP bypassed.
Write-up + exploits: fatgid.io/
Michał Purzyński retweeted
Step beyond traditional talks and explore the new world of CONFidence Villages.
Dedicated spaces built around specific areas of cybersecurity, technology, and hands-on learning - from Radio Hacking and Hardware Hacking to IoT, Speedrunning, CTFs and more.
🤖 Made with AI
Michał Purzyński retweeted
amd.com/en/resources/product… Xen advisory posted, should be a kernel fix here any minute now I assume
Michał Purzyński retweeted
𝟮. They built a word for work-life balance instead of just talking about it.
𝘍𝘦𝘪𝘦𝘳𝘢𝘣𝘦𝘯𝘥.
The sacred end of the working day.
In Germany, when work ends – it ends.
Google signs classified AI deal with Pentagon, The Information reports reut.rs/4cVSh0p reut.rs/4cVSh0p
Michał Purzyński retweeted
After burning $2.5k on tokens and LLM findings, I have a question about the 270 Firefox bugs: were they all attacker-reachable? The findings I got where often "legitimate bad code" but also "not reachable in any sane scenario".
Michał Purzyński retweeted
A lot of people have been DM’ing us asking:
"What can we actually do with the #CONFibadge?"
So let us answer this one publicly.
What if you plugged in an #OBD2 adapter and explored what "car hacking" looks like - in a controlled, educational scenario?
Michał Purzyński retweeted
WIRED (@WIRED) has gone ahead with publishing an extraordinarily inaccurate article about GrapheneOS. It presents a highly inaccurate history of the GrapheneOS project heavily based on fabrications from James Donaldson. WIRED failed to incorporate most of our responses to his inaccurate claims.
Donaldson has fabricated a whole alternate history of the project and Copperhead including leaving out the fact that it had 3 co-founders rather than 2. Donaldson lived off income brought in by Daniel's open source project created prior to the company. He certainly didn't fund it as he claims.
Prior to publishing the article, a fact checker at WIRED asked us a long series of questions about the project. These questions made it extremely clear that the article was largely sourced from fabrications from Donaldson despite it not being specified. It's not a real history of GrapheneOS at all.
Our community manager spring-onion (Dave Wilson) handled nearly all of the communications with WIRED. He's a public-facing member of our moderation team and well known in our community. WIRED first reached out to Daniel, promised the story wouldn't be about him and were handed off to spring-onion.
WIRED heavily misled about the article. They led us to believe the article would be about GrapheneOS with little coverage of the history. They repeatedly reassured us it would hardly have any of the content it ended up being based around. Therefore, we had no opportunity to properly address it.
We made a forum post at discuss.grapheneos.org/d/343… which contains an overview of the situation along with the unmodified answers we provided to WIRED's fact checker. You can see for yourself what we provided and that it wasn't anywhere close to adequately incorporated into the article.
After the article was submitted, we received that list of questions from WIRED's fact checker. We realized the article was largely going to be a fake account of the history of the project based on Donaldson's claim. That's when we made these posts:
teapawt.net/GrapheneOS/status/2043…
bsky.app/profile/grapheneos.…
A small portion of our response to those questions was incorporated, but not most of it. There's also more we weren't asked about which we can now see is in the article. We tried to address that at in the initial overview at discuss.grapheneos.org/d/343… prior to the submitted answers.
The editors of Wired (@WIRED) appear determined to turn an article about GrapheneOS into a hit piece. Wired contacted James Donaldson, CEO of Copperhead, and appears to be treating his thoroughly debunked fabrications about the history of the project as their primary source. This is outrageous.
Wired wants a clickbait article with lots of controversy and isn't accepting it without it. We spent months talking to the author of the story and received repeated assurances about how it was being approached. The author of the article was clearly pressured into making it an inaccurate hit piece.
We're posting this to reach someone at Wired who can pause this and have it handled with the appropriate care it needs. Sourcing an article about GrapheneOS from a person who has spent years trying to harm us and is losing a legal battle including having to withdraw these claims makes no sense.
Israeli strike kills infant girl in south Lebanon during father's funeral reut.rs/4tCwsJV reut.rs/4tCwsJV



























