On Tue, Jan 20, 2026 at 7:45 PM Stuart Henderson <[email protected]> wrote:
> On 2026-01-20, Washington Odhiambo <[email protected]> wrote: > >> On Tue, Jan 20, 2026 at 05:41:13PM +0300, Washington Odhiambo wrote: > >> > Putty/Bitvise SSH clients work with all VMs, and all hosts that I > manag= > > e, > >> > but NOT OpenBSD. > > very strange. > > btw putty 0.83 can connect ok to 7.8 and -current here. > > >> > Any ideas? > >> > >> Run sshd on the OpenBSD machine in the foreground from the console to > see > >> comprehensive debugging info: > >> > >> # /etc/rc.d/sshd stop > >> # /usr/sbin/sshd -ddd > >> > >> This will generate a lot of output, but will allow you to see how the > ssh > >> session is being negotiated, (and hopefully identify where it fails). > >> > > > > Here is the debug info: https://paste.ubuntu.com/p/CXP2qNWWTX/ > > this isn't IRC, you can just include that directly in the email. > it's easier for other people reading, and won't expire in case > somebody later looks at this in the list archives. > > So putty drops the connection before auth'ing: > > debug1: SSH2_MSG_NEWKEYS sent [preauth] > debug1: Sending SSH2_MSG_EXT_INFO [preauth] > debug3: send packet: type 7 [preauth] > debug1: expecting SSH2_MSG_NEWKEYS [preauth] > Connection closed by 192.168.69.109 port 5821 [preauth] > debug1: monitor_read_log: child log fd closed > > I think you need to look at logging on the putty side to see what > it's doing. Go to session logging, set it to 'SSH packets', try to > connect, then take a look in putty.log (or whatever other filename > you used). > Using Solarwinds Putty client works! Byebye other putty. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]
