Christophe CasalegnoAutoimmune warrior, Entrepreneur & Bio/Hacker

StackX OpenSSH: security fixes for Debian 9, 10 and 11

After all the fixes I’ve had to backport lately (Linux kernels, PHP 5.6 through 8.5, Apache…), I’m continuing with StackX OpenSSH for Debian 9 Stretch, Debian 10 Buster and Debian 11 Bullseye machines that need to keep running until our clients can finish (or sometimes start) their migration.

I started with the sources for each Debian release. For Stretch and Buster, I used the Debian sources with the fixes Freexian had already applied. For Bullseye, I started from the Debian LTS revision published with advisory DLA-4584-1. I backported fixes from OpenSSH 10.4 through 10.6p2 wherever the affected code existed in our branches, then rebuilt the packages on their original base.

That’s why you’ll still see OpenSSH 7.4p1 on Stretch, 7.9p1 on Buster and 8.4p1 on Bullseye. To find out which fixes you have on a machine, check the full Debian package version. For the server package, for example, run dpkg-query -W openssh-server.

Packages available as of 19 November 2026

DebianPublished revision for amd64CVEs addressed by the StackX changes
9 Stretch1:7.4p1-10+deb9u12+sx814
10 Buster1:7.9p1-10+deb10u7+sx816
11 Bullseye1:8.4p1-5+deb11u7+sx817

The fixes cover the SFTP client, tunnel restrictions, GSSAPI and SSH compression, among other things. Each repository contains openssh-client, openssh-server, openssh-sftp-server and ssh, along with their sources and the companion packages for that distribution. The release notes list the changes and remaining limitations for Stretch, Buster and Bullseye.

What I checked

I built and tested all three revisions in isolated VMs. I installed the four main packages through APT on each Debian release. The tests covered authentication, SFTP transfers and rekeying during a session. APT also rejected the repository when tested with a tampered signature or a different key.

Once the repositories were online, I verified all three InRelease signatures, checked the indexes and compared the checksums of all 17 packages I downloaded. You can find the signed indexes for Stretch, Buster and Bullseye.

What happens to my sshd_config with +sx8?

On several Stretch machines, the upgrade to +sx7 asked me whether to replace the local sshd_config. If I’ve configured SSH to listen on a particular port, I want it to keep listening on that port after the upgrade, without having to answer the same question on every machine.

That’s what changes in +sx8. If /etc/ssh/sshd_config exists, the package keeps it by default without prompting. If you’ve set your own ucf policy, it still takes precedence. The OpenSSH fixes are the same ones shipped in +sx7.

I verified in VMs that upgrading to +sx8 preserved a custom SSH port on all three distributions. On Buster, I also verified under systemd that the SSH service restarted automatically during the upgrade and that I could open a new connection. I still need to run that last test on Stretch and Bullseye.

Adding the repository and upgrading

  1. Keep an SSH session open and make sure you have another way in, such as the server console. Back up /etc/ssh/, including the host keys, and keep the old packages so you can roll back.
  2. Open the installation guide for Debian 9 Stretch, Debian 10 Buster or Debian 11 Bullseye (in French). Download and read that distribution’s add-stackx-openssh-repo.sh before running it as root. It checks the distribution, architecture, key fingerprint, repository signature and package index, then configures APT with signed-by. It installs no OpenSSH packages and does not restart SSH.
  3. Check the versions APT offers and simulate upgrading the four packages together, using the exact versions in the guide. Include any companion packages you use in the simulation. Review the result before installing with --no-remove during a maintenance window. On Stretch, check your configuration if you use GSSAPI. Combining it with UsePrivilegeSeparation no is now rejected.
  4. After installation, check the configuration with sshd -t, then open a new connection on the expected port. Test what you actually use on that machine before closing your original session.

You’ll find the packages, sources and setup script for each distribution on the StackX OpenSSH mirror. For the sources behind the backports, see the OpenSSH release notes, Freexian’s advisories for Stretch and Buster, and the Debian LTS advisory for Bullseye.

--
Christophe Casalegno
https://all.bo

Christophe Casalegno Brain 0verride

Keep it simple
and direct!