- cross-posted to:
- technology@lemmy.ml
- cross-posted to:
- technology@lemmy.ml
cross-posted from: https://lemmy.pt/post/5733711
A severe vulnerability in OpenSSH, dubbed “regreSSHion” (CVE-2024-6387), has been discovered by the Qualys Threat Research Unit, potentially exposing
Question if I update my server and it has the new SSH (patched) package. Is that enough or do I have to restart the server as well? How can I check if the old SSH is in use currently?
Some package managers have a command to see if anything is in need of restart. Zypper has ps -s for example. I’d restart to be sure though.
My server tells me a restart would be required because of:
Does that have anything to do with the SSH package?
It sounds like it’s the kernel but whether it has anything to do with ssh, I really don’t know. Sometimes parts work together in surprising ways, as I learned with the recent sshd/systemd/xz exploit.
You might be fine and this was the most alarming exploit since it’s very inconvenient, but personally I’d restart just to be sure.
Restart your ssh server to be sure (probably
sudo systemctl restart sshd). No need to reboot your server for this.I don’t know how reliable this is, but I usually go into htop to check if stuff needs to be restarted. Processes in red have been replaced or removed since starting.
That said, regular server reboots are a good idea to make sure kernel patches are applied. Can’t go wrong with a reboot just in case.
we do restarts twice a month, they are in production
Well I should have read the first comment before I went ahead with update and reboot😪
For anyone in RHEL / Fedora land (or using dnf somewhere else), try
dnf needs-restartingto list executables that have mismatched files on disk vs memory. The-rflag will hint if a reboot is needed (due to things like kernel or glibc changes)