Date: Thu, 1 Aug 2002 21:32:20 +0200 From: Thomas Seck <tmseck-lists@netcologne.de> To: stable@FreeBSD.ORG Subject: Re: SSHD for protocol version 2 changed? Message-ID: <20020801193220.GA1052@laurel.tmseck.homedns.org> In-Reply-To: <000701c23959$3ae2a640$0b64a8c0@pootah> References: <20020718041640.GA169@leafy.idv.tw> <20020718093542.Q53886-100000@www.mmlab.cse.yzu.edu.tw> <200207180204.g6I244Je000390@drugs.dv.isc.org> <20020718041640.GA169@leafy.idv.tw> <1026966873.18062.26.camel@chowder.gsoft.com.au> <5.1.1.6.2.20020731075139.022604e8@194.184.65.7> <20020731111228.B93345@veverka.sh.cvut.cz> <007001c23882$d5c72fa0$0b64a8c0@pootah> <000701c23959$3ae2a640$0b64a8c0@pootah>
next in thread | previous in thread | raw e-mail | index | archive | help
* Rob B (rbyrnes@ozemail.com.au): > A question was raised in this thread about what triggers the illegal > operation in PuTTY when connecting. > > Compression OFF + Keyboard interactive OFF = OK > Compression ON + Keyboard interactive OFF = OK > Compression OFF + Keyboard interactive ON = dead PuTTY > Compression ON + Keyboard interactive ON = dead PuTTY Strange, I tried but I cannot confirm this. PuTTY 0.52 on Windows XP against OpenSSH 3.4p1 FreeBSD-20020702 from a system built on July 20 works fine here with every combination of authentication method, compression, encryption algorithm, and "Keyboard Interactive"-ness I could think of. > So as I stated in a previous mail - it doesn't matter whether you use > comperession on the ssh session, it's the keyboard interactive bit that > kills PuTTY. Hm, not here. Seems to be a bit more complicated. -- Thomas Seck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020801193220.GA1052>