Don't waste your time listening to podcast ads. Try @SkipperTheApp for iPhone, Mac, and iPad. It detects and skips ads using 100% on device intelligence which allows us to avoid charging a subscription fee.
brick retweeted
I am begging people to use rss
Where do I get my cybersecurity news? r/netsec, almost every day.
It's not polished, there's no editor chasing clicks, it's just hackers and security practitioners posting stuff they found interesting. Half the time I learn about a new technique from a comment thread arguing about it, not even the post itself.
If your news diet is press releases and breach headlines, go spend ten minutes in there instead.
brick retweeted
Oh FFS. Thank you for your concern Sam, but don’t spread your FUD and doom bait in my waters.
I lead one of the most utilized Linux operating systems in the world for data centers and enterprises, and I founded its predecessor too.
While AI is surely accelerating finding human created security issues, it is a temporary problem, and most open source project leads have already figured out how to also use AI to reduce new bugs moving forward.
Here is a graph from GKH (who maintains the stable kernel) on how many CVEs they are remediating per release:
github.com/gregkh/kernel-dev…
This graph describes how much better each release is now getting:
github.com/gregkh/kernel-dev…
This doom based marketing approach that the AI labs are pushing is really short sighted. While this will of course drive business to us, I find it unethical to distort the truth and use scare tactics in messaging.
The greater truth is that AI is making the software industry more secure, by identifying the human errors in code, and soon we will end up in a much better place.
🚨Sam Altman says the internet can no longer be SECURED by patching bugs.
"I no longer think we're going to be able to just patch all the bugs," the OpenAI CEO said, warning smarter models can find "hardware level insane stuff."
He says OpenAI can't responsibly open source its best model "anytime soon," but the open source world isn't far behind: "Not super."
brick retweeted
The php2shell thing quickly showed me how little most people know about how memory management works and how hard things like this are to actually port into a reliable exploit.
My first thought looking at the vulns was “this is neat” not that the internet was going to break.
So far I’m glad I turned out to be mostly right I suppose.
People think firms like Jane Street are filled with unfettered geniuses but really most of there advantage comes from being able to afford _the fastest_ network connections, compute, inference, etc.
It takes smarts to use those things well but its not like they are the only people on the planet that could do it.
brick retweeted
The COVID analogy fits more and more on the PHP security issue.
Everybody is expert now, missinformation spread faster than light,
doomsdayer are spreading more and more serious accusations.
If I were a hacker, I'd ignore the vulnerability in PHP, but instead jump on mass histeries, pretend I'm expert, offer service, solution or unofficial but "much faster patched PHP" binary image, plot a backdoor there and do real hacking.
As social networks and Google promote polarizedi information over correctness and factuality, this should work pretty neatly.
brick retweeted
Don’t get too worked up. The vast majority of these vulns are not exploitable or if exploited wouldn’t cause any harm.
Most of the AI driven vuln discoveries are background noise that is only interesting becuase it create the volume you see in the graph, and panic from those who don’t understand it.
I explained this in a series of videos about Mythos just after it was released.
youtu.be/wQvobgIFHXo?is=5LWA…
brick retweeted
We’ve seen plenty of php2shell probes and exploitation attempts in our honeypots.
At the time of writing, we’ve observed no successful remote code execution and no dropped PHP files.
Reliable RCE may be harder to achieve than initially expected.
What we’re seeing now could change in the future as public research continues.
CVE-2026-109618 & CVE-2026-109619

















