The DevOps Guy retweeted
There are two types of software vulnerabilities being exposed in the AI age:
1. AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
2. 4
3. Off by Ones
The DevOps Guy retweeted
We built a game to teach DevOps 🏘️
Opsville is a free pixel-art town where every district is broken and you are on call. Each quest opens a real simulator: Linux, Docker, Git, CI/CD, Kubernetes.
Play free in your browser at DevOps Daily.
The DevOps Guy retweeted
I'm not even sounding the claxon for this it's just horrible.
Any text > 256chars is a valid root password, holy shit
sshhole.com/
The DevOps Guy retweeted
Mark November 11 date in your calendar for security updates.
Security release pre-alert:
We will release new versions of Node.js 22, 24, and 26 release lines on or shortly, after 2026-11-11 in order to address security vulnerabilities.
The highest severity issue fixed in this release is HIGH.
nodejs.org/en/blog/vulnerabi…
Security release pre-alert:
We will release new versions of Node.js 22, 24, and 26 release lines on or shortly, after 2026-11-11 in order to address security vulnerabilities.
The highest severity issue fixed in this release is HIGH.
nodejs.org/en/blog/vulnerabi…
The DevOps Guy retweeted
It’s just amazing how many people think DevOps = writing YAML.
> prod incidents
> on-call rotations
> rollbacks without data loss
> zero-downtime migrations
> database upgrades
> cluster upgrades
> IAM and security sign-off
> secrets management
> certificate renewals
> networking, DNS, TLS
> firewall and VPC design
> capacity planning
> scaling under real traffic
> load testing
> cost control
> backups that restore
> disaster recovery
> multi-region failover
> compliance and audits
> access reviews
> patching CVEs
> observability and alerting
> killing noisy alerts
> root cause analysis
> postmortems
> vendor outages
> release coordination
> change management
> dev environment hell
> legacy tribal knowledge
> onboarding engineers
> saying no to shiny tools
> owning prod
The DevOps Guy retweeted
Reacting to the full Anthropic S-1 registration statement.
Anthropic has filed an S-1 registration statement with the SEC related to its proposed IPO.
Read more: anthropic.com/news/s1-sec
Legal disclaimer: A registration statement relating to these securities has been filed with the SEC but has not yet become effective. These securities may not be sold, nor may offers to buy be accepted, prior to the time the registration statement becomes effective. This post does not constitute an offer to sell or the solicitation of an offer to buy these securities, nor shall there be any sale of these securities in any state or jurisdiction in which such offer, solicitation or sale would be unlawful prior to registration or qualification under the securities laws of any such state or jurisdiction.
The DevOps Guy retweeted
📝 Why Your @github Actions Bill Keeps Growing, and What Each Fix Saves
Per-job rounding, macOS minutes at ten times the Linux price, re-runs and storage add up quietly.
devops-daily.com/posts/githu…
#DevOps #CICD
The DevOps Guy retweeted
Everyone: "Vibe coding is causing all these security bugs"
Reality: PHP, Node, Linux kernel, GitLab. All hand-written code by humans, some of it 20 years old.
AI isn't creating the slop. It's finding it 🫠
I notified a friend working at a big tech corporate about the PHP vulnerability as their entire infrastructure runs on PHP
He answered
"Thanks, I'll try patch it in a few days as I'm Out of Office (OOO) now"
And this is a modern tech company, imagine the traditional companies running PHP
People won't update fast enough and the vulnerability will be out in the wild once the patch hits as anyone can reverse engineer it based on the patch
Considering this, there's gonna be so many sites hacked and so much user data exposed I think
🤯
I pre-emptively disconnected ALL my sites / VPS servers from the web
I'll wait for the patch to hit at 2 PM UTC
If you have a PHP website, probably good to take them down until you patch PHP
69.3% of the web runs on PHP so this is going to be intense!
Good time maybe to buy cybersecurity stocks? (not financial advice)

































