[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1103418: marked as done (openssh-server irregularly crashing since 10.0p1 upgrade)

Your message dated Wed, 07 May 2025 15:39:16 +0000
with message-id <E1uCgrc-00E0Ml-2O@fasolo.debian.org>
and subject line Bug#1103418: fixed in openssh 1:10.0p1-3
has caused the Debian Bug report #1103418,
regarding openssh-server irregularly crashing since 10.0p1 upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1103418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103418
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: openssh-server
Version: 1:10.0p1-2
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: stittl@cuug.ab.ca

Hi. Since 10.0p1 came out, about half the time I try to connect to my
system it fails and on inspection there is a crash in the dmesg
output:

[419972.562415] sshd-session[189732]: segfault at 7ffceb533dbc ip 00007ff7dc95261d sp 00007ffceb533d70 error 6 in libc.so.6[6261d,7ff7dc918000+165000] likely on CPU 3 (core 3, socket 0)
[419972.562422] Code: 59 ec ff ff e8 a4 a5 0b 00 0f 1f 40 00 41 57 49 89 f7 41 56 49 89 d6 41 55 41 54 55 53 48 89 fb 4c 89 ff 48 81 ec f8 04 00 00 <89> 4c 24 4c 48 89 74 24 70 be 25 00 00 00 64 48 8b 04 25 28 00 00

Of course the addresses and cpu number vary, but the code is always
the same.

Since this started happening a few days ago, I wondered if it might be
because my system had been up for over a year and cthulhu knows how
many versions of libc6 were still pinned in core because a process
still depended on it after an upgrade, but rebooting had no
effect. libc has also upgraded twice since this started, also with no
effect.

Obviously this will require more investigation to debug. I am at your
disposal.

Ta.



-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.14.0 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openssh-server depends on:
ii  debconf [debconf-2.0]       1.5.91
ii  init-system-helpers         1.68
ii  libaudit1                   1:4.0.2-2+b2
ii  libc6                       2.41-7
ii  libcom-err2                 1.47.2-1+b1
ii  libcrypt1                   1:4.4.38-1
ii  libgssapi-krb5-2            1.21.3-5
ii  libkrb5-3                   1.21.3-5
ii  libpam-modules              1.7.0-3
ii  libpam-runtime              1.7.0-3
ii  libpam0g                    1.7.0-3
ii  libselinux1                 3.8.1-1
ii  libssl3t64                  3.5.0-1
ii  libwrap0                    7.6.q-36
ii  libwtmpdb0                  0.73.0-2
ii  openssh-client              1:10.0p1-2
ii  openssh-sftp-server         1:10.0p1-2
ii  procps                      2:4.0.4-8
ii  runit-helper                2.16.4
ii  systemd [systemd-sysusers]  257.5-2
ii  sysvinit-utils [lsb-base]   3.14-4
ii  ucf                         3.0051
ii  zlib1g                      1:1.3.dfsg+really1.3.1-1+b1

Versions of packages openssh-server recommends:
ii  libpam-systemd [logind]  257.5-2
ii  ncurses-term             6.5+20250216-2
ii  xauth                    1:1.1.2-1.1

Versions of packages openssh-server suggests:
pn  molly-guard   <none>
pn  monkeysphere  <none>
pn  ssh-askpass   <none>
pn  ufw           <none>

-- debconf information:
  openssh-server/permit-root-login: true
  openssh-server/password-authentication: true

--- End Message ---
--- Begin Message --- 
Source: openssh
Source-Version: 1:10.0p1-3
Done: Colin Watson <cjwatson@debian.org>

We believe that the bug you reported is fixed in the latest version of
openssh, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1103418@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Colin Watson <cjwatson@debian.org> (supplier of updated openssh package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 07 May 2025 16:18:43 +0100
Source: openssh
Architecture: source
Version: 1:10.0p1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
Changed-By: Colin Watson <cjwatson@debian.org>
Closes: 1103418
Changes:
 openssh (1:10.0p1-3) unstable; urgency=medium
 .
   * Disable --with-linux-memlock-onfault again, since it causes
     RLIMIT_MEMLOCK to be exceeded with some combinations of PAM modules
     (closes: #1103418).
Checksums-Sha1:
 aeeb35c7ad872dee4b89f12d728029d97897e7fb 3500 openssh_10.0p1-3.dsc
 b7b0ab2c14b12a924b28166d511771c24308a60a 198252 openssh_10.0p1-3.debian.tar.xz
Checksums-Sha256:
 dd61e5adff0bc376a99fe32db5efaa7dc59506448864e5f15084fb4691ecc476 3500 openssh_10.0p1-3.dsc
 4f67e8f122222f4b6f5359ab86efc0cc872fe4c48d4d02357f68e18c99679f1a 198252 openssh_10.0p1-3.debian.tar.xz
Files:
 de36ee5b12d04c72ae49907cc712a3fc 3500 net standard openssh_10.0p1-3.dsc
 7c0e01b17b85beedf4c6514617ce7ada 198252 net standard openssh_10.0p1-3.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmgbefEACgkQOTWH2X2G
UAvMuw/+PUDpMqF32OqbTeMq1sGCgCJSyruraG40YoF/WOt9/e5Ivhu0OylE965T
IZK1O3h+5GNy7/MWe6QEBFWHqRCazdVmDegCrHz2RYWO7aE2IDHxJhega3JH5HFH
n6Nk09rPjNMb0qjmXZHgFt699M4sJUuaCLafI7578iHjmnaI1svOZTRLG6wISUJg
a6tmH02YKuCJpQLB1770TKUF7o+Ww7ZeSgPrMReF6+38N/5SrBGyBqIwFureaeOS
UVHS/TkkxpWuE3IJCKeqmgAkZTBDlr69cKv8f6/edjRpKkxWrvSDedu2pHfWYOIq
bPbT2kfL1WaQa4K160uyVQnCteHpeMZfjeTLTB0f5sqy7dz+C0771IyBzUVjXwQX
gjLhvzZGX7FEVPLfkoxgQfEGxSvYarHHjpG4eTiwHa9stzBRDl7Zdm4+cpg5o2dd
17vKSrHhy8W2I0zna5sfpzHST8y3j8v7kK7vwZs0UHwB1Ve/9XcUkkN+CI01iFMZ
t9PVzxJ+jBJiHjanRuXxiQcknTzZBfpEFCjE18XbJE509rpvbhyfqHZYXSUnuG6K
ip43hFS9Ofhrt2eznShMSXlbesJhHyrWtVP2fGDZUPs+N4pDEHaLVEKd3FUU53vu
JKwrmvPT7l6cIXciTgcmuPzqx9bOKM9BLtyWQdD090kXTZfyGPA=
=mcHs
-----END PGP SIGNATURE-----

Attachment: pgpJLQpDld96Y.pgp
Description: PGP signature


--- End Message ---
Reply to: