Articles and guides
How security updates for Linux work, and how to keep a handful of machines - or a few hundred - up to date without it taking over your week.
AI is finding more vulnerabilities - why updating matters more than ever
AI tools are finding vulnerabilities faster than ever, and attackers are exploiting them faster too. What the numbers show, and what it means for keeping Linux machines updated.
The AI tools on your servers are a new attack surface
Agent frameworks, model gateways and inference servers are some of the fastest-growing sources of vulnerabilities. Why they're risky, and how to run them safely.
AI-written code brings its own vulnerabilities
Vulnerabilities traced back to AI coding tools are rising fast, and AI suggests packages that don't exist. What the research shows, and what to do about it.
What is a security update?
The difference between an outdated package and a vulnerable one, what a CVE is, and why most Linux updates aren't security fixes.
Who fixes vulnerabilities in Linux?
How a vulnerability travels from discovery to a fixed package on your machine, and who does the work along the way.
What a critical update means
How Linux distributions rate the severity of vulnerabilities, and how fast a critical security update should be installed.
Choosing when to update
How to keep Linux machines secure without updating everything blindly: separate security fixes from routine updates and plan the sensitive ones.
Who keeps your packages secure?
Distribution packages, Flatpak, the AUR, pip and npm, containers: who tracks vulnerabilities and backports fixes for each, and what that means for your updates.
Planning for end of life
How to keep track of Linux releases approaching end of life across a mixed fleet, and plan the upgrade before support runs out.
Keep track of every machine
OS Checker shows which of your machines have outdated or vulnerable packages, and which releases are approaching end of life - in the terminal, on the web or by email.
Get early access