From owner-freebsd-current Mon Jul 30 7:36:37 2001 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [206.40.252.115]) by hub.freebsd.org (Postfix) with ESMTP id 6F59D37B40D; Mon, 30 Jul 2001 07:36:31 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.4/8.11.1) id f6UEaVP57620; Mon, 30 Jul 2001 07:36:31 -0700 (PDT) (envelope-from obrien) Date: Mon, 30 Jul 2001 07:36:31 -0700 From: "David O'Brien" To: Brian Fundakowski Feldman Cc: current@FreeBSD.org Subject: Re: quick informal survey: OpenSSH broken? Message-ID: <20010730073630.C57400@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200107300154.f6U1sPf39683@green.bikeshed.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107300154.f6U1sPf39683@green.bikeshed.org>; from green@FreeBSD.org on Sun, Jul 29, 2001 at 09:53:09PM -0400 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Jul 29, 2001 at 09:53:09PM -0400, Brian Fundakowski Feldman wrote: > I need to know, if OpenSSH is ever going to get MFC'ed, are there any people > currently running OpenSSH 2.9 from -CURRENT's base and getting major > problems with it? Or even minor ones that actually make things more You've never responded to requests from people asking what it would take to make things fall back to v1 gracefully. We all know it is a "feature" that with a default configuration, it will try ssh2 first and if it is not able to authenticate (say you have no .ssh/authorized_keys2 file) the connection can fail. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message