Bug#1103418: openssh-server irregularly crashing since 10.0p1 upgrade

Colin Watson <[email protected]>
Newsgroups gmane.linux.debian.devel.ssh
Message-ID <aBIcKbAZjFrFKg01__24149.3324328744$1746017496$gmane$org@riva.ucam.org>
On Wed, Apr 30, 2025 at 02:08:47PM +0200, Michel Casabona wrote:
>Le 30/04/2025 à 13:42, Colin Watson a écrit :
>>Is that the complete output from valgrind, or did you edit it down? 
>>It's tantalizingly close to being useful, but it really feels like 
>>there should be more of it.  Could I have all of the lines matching 
>>"==4019365=="?
>
>Yes, I pasted a few line to post, sorry. The full log is attached below.

Thanks.  The leak stuff is basically all noise - I think you can drop 
--leak-check=full as it doesn't really help here.  The interesting bit 
is why sshd-session apparently needs more than the default stack.  The 
lack of a stack trace there makes it difficult to work out context, but 
I think it's probably one of the glob() calls in auth2-pubkey.c.  It 
might be innocent and just be an artifact of running under valgrind; or 
it might point to a deeper problem.

Could you drop --leak-check=full from the valgrind call, and instead add 
--main-stacksize=67108864 (i.e. eight times the current value)?  Then 
provoke the bug again and send me the new valgrind output.  Let's see if 
that tells us something different.

Could I also get your /etc/ssh/sshd_config and /etc/ssh/sshd_config.d/* 
files (of course you can edit out anything secret, but if you do then 
please at least keep the structure)?

Thanks,
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.