From owner-freebsd-stable Thu Aug 1 12:35:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6B8F37B401 for ; Thu, 1 Aug 2002 12:35:51 -0700 (PDT) Received: from smtp.netcologne.de (smtp.netcologne.de [194.8.194.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1763A43E72 for ; Thu, 1 Aug 2002 12:35:46 -0700 (PDT) (envelope-from tmseck-lists@netcologne.de) Received: from localhost (xdsl-213-168-108-94.netcologne.de [213.168.108.94]) by smtp.netcologne.de (8.12.2/8.12.2) with ESMTP id g71JZeUt002995 for ; Thu, 1 Aug 2002 21:35:40 +0200 (MEST) Received: (qmail 1148 invoked by uid 1001); 1 Aug 2002 19:32:20 -0000 Date: Thu, 1 Aug 2002 21:32:20 +0200 From: Thomas Seck To: stable@FreeBSD.ORG Subject: Re: SSHD for protocol version 2 changed? Message-ID: <20020801193220.GA1052@laurel.tmseck.homedns.org> Mail-Followup-To: stable@FreeBSD.ORG 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000701c23959$3ae2a640$0b64a8c0@pootah> User-Agent: Mutt/1.4i Organization: private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 X-Attribution: tms Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * 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