Bug#1129956: openssh-server: Cant login with UsePAM no since upgrade to systemd 260rc2

Colin Watson <[email protected]> Fri, 6 Mar 2026 16:03:37 +0000
Newsgroups gmane.linux.debian.devel.ssh
Message-ID <aar62QGDVH-YdWX___30805.7979027339$1772814077$gmane$org@riva.ucam.org>
On Fri, Mar 06, 2026 at 10:16:59AM -0500, manul wrote:
> I've been running ssh server with the following changes from the defaults:
> 
> PasswordAuthentication yes
> PermitRootLogin yes
> UsePAM no
> 
> It has been working normally since a recent upgrade (including systemd and libpam-systemd to version 260rc2).
> 
> Since the upgrade, the above no more works.
> 
> When I try to ssh to the machine, it reacts as if a wrong password was supplied:

I can't reproduce this.  I created an Incus container using testing, 
created a test user with a password, applied the configuration you gave 
above, tested that I could SSH to it, and then upgraded it to unstable.  
Everything still worked fine.

I suggest temporarily adding "LogLevel DEBUG3" to your configuration, 
restarting sshd, trying again, and sending the resulting debug log to 
this bug report (e.g. `journalctl --unit=ssh.service --since='5 minutes 
ago'` if you're booting with systemd, or otherwise look around in your 
system logs).  The resulting log may have things you consider sensitive 
such as IP addresses, user names, and public keys, so feel free to 
redact anything like that; and you should undo that LogLevel change 
after gathering this information, since it can violate user privacy.

Thanks,