Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2022-07-27 Thread Chris Hofstaedtler
Control: reassign -1 glibc

Dear glibc Maintainers,

this bug appears to be an upgrade issue where (old versions?) of
libc6 might have done something wrong. Maybe you can decide what to
do with/about this bug.

It does not look like openssh-server would be the right place to fix
anything about it.

Chris



Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-20 Thread Russ Allbery
Marco d'Itri  writes:
> On Jan 20, Russ Allbery  wrote:

>> This also implies that there is arguably an SONAME issue with this library
>> given that two versions of the library with the same SONAME don't provide
>> the same symbols, but I suspect there were really, really good reasons to
>> not change the SONAME.

> The upstream maintainers choose to provide backward compatibility to old 
> binaries but not forward compatibility from old libraries.

Oh, yes, that makes sense and is entirey normal.  I was thinking about it
the wrong way around.  So the root problem is that the dependency was
satisfied for the binary but there was a stray copy of the old library
with the same SONAME in an earlier directory on the search path, which
shadowed the correct library.

-- 
Russ Allbery (r...@debian.org)  



Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-20 Thread Marco d'Itri
On Jan 20, Russ Allbery  wrote:

> This also implies that there is arguably an SONAME issue with this library
> given that two versions of the library with the same SONAME don't provide
> the same symbols, but I suspect there were really, really good reasons to
> not change the SONAME.
The upstream maintainers choose to provide backward compatibility to old 
binaries but not forward compatibility from old libraries.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-20 Thread Russ Allbery
Clément Hermann  writes:

> I have the same issue. The symbol is in the file provided by libcrypt1,
> however, it is in /usr/lib.

> what I have in /lib is:

> ```
> ls -l /lib/x86_64-linux-gnu/libcrypt.so.1
> lrwxrwxrwx 1 root root 16 déc.  27 20:31 /lib/x86_64-linux-gnu/libcrypt.so.1 
> -> libcrypt-2.25.so
> ls -l /lib/x86_64-linux-gnu/libcrypt-2.25.so 
> -rw-r--r-- 1 root root 39272 déc.   2  2017 libcrypt-2.25.so

> ```

> The version (2.25) looks like it's a leftover from an older libc6
> package ? no package provides libcrypt-2.25.so as a file. libcrypt has
> been disabled in libc6 2.29-4.

In further support of this theory, neither my continuously-upgraded
unstable system nor my continuously-upgraded testing system have that
file.  The testing system was built in 2014; the unstable system in late
December 2017 (so that may not be as interesting).  (Neither of those
hosts are using merged-/usr, just to say explicitly.)

I think that argues that there was some cleanup step that happened for
some systems but not for others.

> It looks like a leftover or something. Removing the file and running
> ldconfig fixes the issue for me (but now I wonder if I have other
> leftover files like this…).

This also implies that there is arguably an SONAME issue with this library
given that two versions of the library with the same SONAME don't provide
the same symbols, but I suspect there were really, really good reasons to
not change the SONAME.

-- 
Russ Allbery (r...@debian.org)  



Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-20 Thread Clément Hermann
On Sat, 18 Jan 2020 23:55:10 +0100 Marco d'Itri  wrote:
> On Jan 07, Guillaume Brocker  wrote:
> 
> > janv. 06 11:10:46 sigismund sshd[27148]: /usr/sbin/sshd: 
> > /lib/i386-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required 
> > by /usr/sbin/sshd)
> Does purging libxcrypt1 make it work?
> 
> If you can confirm this then I will make the next libcrypt1 conflict 
> with it. I did not expect for libxcrypt1 to be still around since it was 
> not shipped in buster and nobody really ever used it.

I have the same issue. The symbol is in the file provided by libcrypt1, 
however, it is in /usr/lib.

what I have in /lib is:

```
ls -l /lib/x86_64-linux-gnu/libcrypt.so.1
lrwxrwxrwx 1 root root 16 déc.  27 20:31 /lib/x86_64-linux-gnu/libcrypt.so.1 -> 
libcrypt-2.25.so
ls -l /lib/x86_64-linux-gnu/libcrypt-2.25.so 
-rw-r--r-- 1 root root 39272 déc.   2  2017 libcrypt-2.25.so

```

The version (2.25) looks like it's a leftover from an older libc6 package ? no 
package provides libcrypt-2.25.so as a file. libcrypt has been disabled in 
libc6 2.29-4. 
It looks like a leftover or something. Removing the file and running ldconfig 
fixes the issue for me (but now I wonder if I have other leftover files like 
this…).

Anyway, I think the bug, if it's not a local problem, isn't in openssh-server, 
but more in libc6, and an old version...

Cheers,

-- 
nodens



Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-19 Thread Guillaume Brocker

Well, libxcrypt1 is not installed on my system. Only libcrypt1 is.

Le 18/01/2020 à 23:55, Marco d'Itri a écrit :

On Jan 07, Guillaume Brocker  wrote:


janv. 06 11:10:46 sigismund sshd[27148]: /usr/sbin/sshd: 
/lib/i386-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by 
/usr/sbin/sshd)

Does purging libxcrypt1 make it work?

If you can confirm this then I will make the next libcrypt1 conflict
with it. I did not expect for libxcrypt1 to be still around since it was
not shipped in buster and nobody really ever used it.





Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-18 Thread Marco d'Itri
On Jan 07, Guillaume Brocker  wrote:

> janv. 06 11:10:46 sigismund sshd[27148]: /usr/sbin/sshd: 
> /lib/i386-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required 
> by /usr/sbin/sshd)
Does purging libxcrypt1 make it work?

If you can confirm this then I will make the next libcrypt1 conflict 
with it. I did not expect for libxcrypt1 to be still around since it was 
not shipped in buster and nobody really ever used it.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#948318: openssh-server: Unable to restart sshd restart after upgrade to version 8.1p1-2

2020-01-07 Thread Guillaume Brocker
Package: openssh-server
Version: 1:8.1p1-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading openssh-server from version 8.1p1-1 to version 8.1p1-2, using 
the apt command line tool, the sshd service failed on restart. Please see below 
the corresponding log entries :
janv. 06 11:10:46 sigismund systemd[1]: Starting OpenBSD Secure Shell server...
janv. 06 11:10:46 sigismund sshd[27148]: /usr/sbin/sshd: 
/lib/i386-linux-gnu/libcrypt.so.1: version `XCRYPT_2.0' not found (required by 
/usr/sbin/sshd)
janv. 06 11:10:46 sigismund systemd[1]: ssh.service: Control process exited, 
code=exited, status=1/FAILURE
janv. 06 11:10:46 sigismund systemd[1]: ssh.service: Failed with result 
'exit-code'.
janv. 06 11:10:46 sigismund systemd[1]: Failed to start OpenBSD Secure Shell 
server.
janv. 06 11:10:46 sigismund systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 1.
janv. 06 11:10:46 sigismund systemd[1]: Stopped OpenBSD Secure Shell server.

Manual installation of the previous version brought sshd functionnal again.

Best regards,
Guillaume

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 5.3.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssh-server depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.73
ii  dpkg   1.19.7
ii  libaudit1  1:2.8.5-2+b1
ii  libc6  2.29-7
ii  libcom-err21.45.4-1
ii  libcrypt1  1:4.4.10-10
ii  libgssapi-krb5-2   1.17-6
ii  libkrb5-3  1.17-6
ii  libpam-modules 1.3.1-5
ii  libpam-runtime 1.3.1-5
ii  libpam0g   1.3.1-5
ii  libselinux13.0-1
ii  libssl1.1  1.1.1d-2
ii  libsystemd0244-3
ii  libwrap0   7.6.q-30
ii  lsb-base   11.1.0
ii  openssh-client 1:8.1p1-2
ii  openssh-sftp-server1:8.1p1-2
ii  procps 2:3.3.15-2+b1
ii  runit-helper   2.8.14
ii  ucf3.0038+nmu1
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  244-3
ii  ncurses-term 6.1+20191019-1
ii  xauth1:1.0.10-1

Versions of packages openssh-server suggests:
pn  molly-guard   
pn  monkeysphere  
pn  rssh  
pn  ssh-askpass   
pn  ufw   

-- Configuration Files:
/etc/ufw/applications.d/openssh-server [Errno 2] Aucun fichier ou dossier de ce 
type: '/etc/ufw/applications.d/openssh-server'

-- debconf information:
* ssh/use_old_init_script: true
  openssh-server/permit-root-login: true
  ssh/vulnerable_host_keys:
  ssh/disable_cr_auth: false
  ssh/new_config: true
  ssh/encrypted_host_key_but_no_keygen:
  openssh-server/password-authentication: true