- cross-posted to:
- linux@lemmy.ml
- cross-posted to:
- linux@lemmy.ml
cross-posted from: https://lemmy.ml/post/46701277
I’ve been running my home lab since 2021 and honestly thought my update routine was solid: apt update && apt upgrade, reboot, job done.
Turns out I was wrong. I was checking CVE‑2026‑31431 (Copy Fail) this morning and realised that despite my “successful” updates, I was still running a vulnerable kernel from March.
I’ve had to rethink how I handle host updates. If you’re relying on a standard upgrade and a reboot to keep Proxmox or Debian hosts safe, you might want to check if yours is lying to you as well.
You must log in or # to comment.
Ooof, scared me there for a second. Good thing I am using Dist-Upgrade in my ansible scripts.
Hmm. Welp. Let’s try. See what happens.
I’ve seen that the patches are only available in the debian-security repository. It’s important to review your repo list in
/etc/apt/sources.list.d.Proxmox does not use the standard debian kernel.
Yes, I referred to the Debian part only.
You’re not supposed to run apt upgrade in Proxmox at all, it may even break your system. Use dist-upgrade.
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#system_software_updates
Just don’t use any command in proxmox. Proxmox is designed GUI first. It got an update button in the GUI. Only major releases could need tinkering in the terminal. But even changing repos is now possible in the GUI.
Gets annoying soon if you have more than one host. Easily automated with Ansible
dist-upgrade and full-upgrade are essentially the same command but yeah, I won’t be using apt upgrade again in the future! Like I said in my post, the joys of being self taught is that you learn by my making mistakes and that’s part of the “fun” 🤣
Nah, the fun is learning form others mistakes. Thanks for a fun read :}
Not essentially, exactly. One is a deprecated alias for the other.
Which one is which?
