Ubuntu 22.04(含Server及Surface端)RegreSSHion漏洞修复补丁应用问题咨询
Hi there, sorry to hear you're stuck trying to get the RegreSSHion vulnerability fix installed on your Ubuntu 22.04 running on a Surface. Let's work through some troubleshooting steps to get this sorted:
First, check if security update repositories are enabled
Ubuntu's security patches (including this OpenSSH fix) are distributed through thejammy-securityrepository. Open the/etc/apt/sources.listfile with a text editor (likesudo nano /etc/apt/sources.list) and verify you have lines similar to these:deb http://archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverse deb-src http://archive.ubuntu.com/ubuntu jammy-security main restricted universe multiverseIf these lines are missing, add them, save the file, and run
sudo apt updateagain.Check your current OpenSSH version
Let's confirm if you already have the patched version installed. Run this command:dpkg -l openssh-server openssh-clientLook at the
Versioncolumn in the output. If it shows1:8.9p1-3ubuntu0.10, the fix is already applied! You might just need to restart the SSH service to make sure it takes effect:sudo systemctl restart sshdForce an upgrade of OpenSSH packages
If your repositories are set up correctly but the update didn't trigger, try explicitly upgrading just the OpenSSH packages:sudo apt update && sudo apt install --only-upgrade openssh-server openssh-clientThis command focuses solely on upgrading these two packages, ensuring you get the latest security patch.
Clear APT cache and retry
Sometimes stale cache data can prevent updates from pulling the latest packages. Try clearing the cache and running updates again:sudo apt clean && sudo apt update && sudo apt upgradeSurface-specific considerations
Some Ubuntu installations on Surface devices use custom repositories or hardware-adapted configurations. If you've modified your sources list before, revert to the default security repositories first. Also, ensure your system isn't set to delay security updates (this is rare for personal setups, but worth checking).
If none of these steps work, take a look at the output of sudo apt update for any error messages (like network issues or unreachable repositories) — sharing those details would help pinpoint the problem further.
备注:内容来源于stack exchange,提问作者abhi

