Date: Tue, 26 Apr 2022 14:27:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 263489] sshd does not work after reboot to 13.1-RC4 Message-ID: <bug-263489-227-TxXwoEbFZE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-263489-227@https.bugs.freebsd.org/bugzilla/> References: <bug-263489-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263489 --- Comment #3 from rob2g2 <rob2g2-freebsd@bitbert.com> --- had another instance today, again different hardware. Now with some more details: *) my sshd_config only uses ed25519, having the line "HostKey /etc/ssh/ssh_host_ed25519_key" in my config *) reconnection after upgrade to RC4 works, after the finishing process of executing "freebsd-update install" it seems I cannot connect any more.=20 *) dmesg: Apr 26 13:56:16 hpnb2 sshd[32523]: fatal: recv_rexec_state: parse config: incomplete message Apr 26 13:56:20 hpnb2 sshd[33082]: fatal: recv_rexec_state: parse config: incomplete message *) before rebooting I switched loglevel to DEBUG in sshd_config, and I got: Apr 26 13:56:16 hpnb2 sshd[37588]: debug1: fd 5 clearing O_NONBLOCK Apr 26 13:56:16 hpnb2 sshd[37588]: debug1: Forked child 32523. Apr 26 13:56:16 hpnb2 sshd[32523]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8 This just happens once, so a restart of the sshd service solves the problem, however, imho this should be done automatically when running freebsd-update after the reboot, otherwise I guess quite some users will forget to manually restart the service and will be locked out if they only have remote access. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-263489-227-TxXwoEbFZE>