[Bug 3666] sshd crash
    bugzilla-daemon at mindrot.org 
    bugzilla-daemon at mindrot.org
       
    Fri Feb  9 09:46:01 AEDT 2024
    
    
  
https://bugzilla.mindrot.org/show_bug.cgi?id=3666
Darren Tucker <dtucker at dtucker.net> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at dtucker.net
--- Comment #1 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to Pawan Badganchi from comment #0)
> This is regarding sshd crash.
What makes you think this is a crash?
> sshd crash is being observed during openssh ptest running everytime
> and it's reproducible.
> Currently we are maintaining dunfell version openssh_8.2p1.
This seems to refer to a version of Yocto, and ptest is some kind of
package test?
> Below is the error message we get. How can i resolve this issue?
> Could you please help here?
> 
> sshd[27514]: Connection from UNKNOWN port 65535 on UNKNOWN port 65535
> sshd[27514]: debug1: Local version string SSH-2.0-OpenSSH_8.2
> sshd[27514]: error: kex_exchange_identification: Connection closed
> by remote host
This means that something (presumably caused by your ptest) to invoke
sshd in a way that did not involve a TCP connection (eg running sshd
-i) then immediately disconnecting.
>  debug1: inetd sockets after dupping: 3, 4
>  bmt sshd[27580]: Connection from UNKNOWN port 65535 on UNKNOWN port
> 65535
>  debug1: Local version string SSH-2.0-OpenSSH_8.2
>  sshd[27580]: error: kex_exchange_identification: client sent
> invalid protocol identifier ""
This is more or less the same, with the difference being that whatever
it was sent an empty initial protocol identifier (probably a newline).
If your tests are invoking sshd to test it, they should probably use -e
to write its logs to stderr or -E to write it to a file rather than
letting it write to syslog.
-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
    
    
More information about the openssh-bugs
mailing list