This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: Does anyone have ssh problem with glibc 2.31?
- From: Florian Weimer <fweimer at redhat dot com>
- To: "H.J. Lu" <hjl dot tools at gmail dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Fri, 14 Feb 2020 16:13:15 +0100
- Subject: Re: Does anyone have ssh problem with glibc 2.31?
- References: <CAMe9rOos7cA9k4+hkucG2XBX_SKH2DfbDc=4w=DvkMS+Suxm8A@mail.gmail.com>
* H. J. Lu:
> I got a report that ssh to localhost didn't work with glibc 2.31:
>
> $ ssh -vv test@localhost
> verify journalctl for messages like
> Feb 13 16:11:12 clr-c8ac6e4ce4c94ca4ac9188a967175ec3 sshd[297]: Server
> listening on :: port 22.
> Feb 13 16:11:59 clr-c8ac6e4ce4c94ca4ac9188a967175ec3 sshd[313]:
> pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0
> tty=ssh ruser= rhost=127.0.0.1 user=test
>
> They had to downgrade to glibc 2.30. Has anyone seen anything similar?
It's seccomp-related. OpenSSH and systemd need updating.
Thanks,
Florian