Bug#1103418: openssh-server irregularly crashing since 10.0p1 upgrade
Colin Watson <[email protected]>
| Newsgroups | gmane.linux.debian.devel.ssh |
|---|---|
| Message-ID | <aBt1K569HVOIttp___3350.0286213652$1746630235$gmane$org@riva.ucam.org> |
Control: forwarded -1 https://bugzilla.mindrot.org/show_bug.cgi?id=3822 On Tue, May 06, 2025 at 07:28:59PM +0200, Michel Casabona wrote: >Sorry for the delay. Here are the results from some testing. >It seems that the problem may be related to pam_ecryptfs, after all [...] >* To exclude any local things and remnants from years of experiments >on my desktop machine, I've setup new virtual machines >(using libvirt / virt-manager, AMD64, UEFI if that matters) as follows: > >- install trixie with the Debian installer Trixie Alpha 1 (netinst) >- no desktop, only ssh server >- add a few convenience packages (sudo mc vim) >- add debugging packages (systemd-coredump, gdb, debuginfod, valgrind) >at this point ssh seems to work correctly > >- add ecryptfs-utils (+ cryptsetup / rsync) >then ssh-session starts to crash most of the time Thanks, this was extremely helpful! I was finally able to reproduce this bug, and tracked it down to the --with-linux-memlock-onfault configure option. I forwarded this to https://bugzilla.mindrot.org/show_bug.cgi?id=3822. I'm going to disable this option again for now, as it's a recent addition and isn't security-critical.