From owner-freebsd-stable Fri Jul 12 19:48: 1 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 32D7C37B401 for ; Fri, 12 Jul 2002 19:47:59 -0700 (PDT) Received: from smtp.noos.fr (verlaine.noos.net [212.198.2.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id F21D743E6D for ; Fri, 12 Jul 2002 19:47:56 -0700 (PDT) (envelope-from root@gits.dyndns.org) Received: (qmail 31778895 invoked by uid 0); 13 Jul 2002 02:47:55 -0000 Received: from unknown (HELO gits.gits.dyndns.org) ([212.198.229.153]) (envelope-sender ) by 212.198.2.73 (qmail-ldap-1.03) with SMTP for ; 13 Jul 2002 02:47:55 -0000 Received: from gits.gits.dyndns.org (872er3hyguem06iz@localhost [127.0.0.1]) by gits.gits.dyndns.org (8.12.5/8.12.5) with ESMTP id g6D2lsdT004531; Sat, 13 Jul 2002 04:47:55 +0200 (CEST) (envelope-from root@gits.dyndns.org) Received: (from root@localhost) by gits.gits.dyndns.org (8.12.5/8.12.5/Submit) id g6D2lsjF004530; Sat, 13 Jul 2002 04:47:54 +0200 (CEST) (envelope-from root) Date: Sat, 13 Jul 2002 04:47:54 +0200 From: Cyrille Lefevre To: Jay Sachs Cc: Doug Barton , stan , FreeBSD Stable Mailing List , des@FreeBSD.org Subject: Re: ssh to remote machines problem after cvsup Message-ID: <20020713024753.GH2527@gits.dyndns.org> Mail-Followup-To: Cyrille Lefevre , Jay Sachs , Doug Barton , stan , FreeBSD Stable Mailing List , des@FreeBSD.org References: <20020708152519.O84324-100000@zoot.corp.yahoo.com> <3D2A2A60.4090807@eziba.com> <3D2B18C9.B266193A@FreeBSD.org> <3D2B270B.2050201@eziba.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3D2B270B.2050201@eziba.com> User-Agent: Mutt/1.3.99i Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[< List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 09, 2002 at 02:10:19PM -0400, Jay Sachs wrote: > Doug Barton wrote: > > Jay Sachs wrote: > > > There are those of us who consider the protocol switch a good change, > > So you are free to do that on your systems. The problem is, whether you > > think it's a good idea or not, it's already catching people by surprise, > > and locking them out of their systems. The change should be reverted. > > It just seems that changes are being made in response to vocal users who > read neither UPDATING nor the headsup to the -stable list. > Unfortunately, when changes feel "right" to people, it's typical > to remain silent; hence I voiced my preference, being a -stable tracker > but non-committer. the problem here isn't the Protocol switch which is valiable. it is the OpenSSH bug which fail to fallback from v2 to v1 when not available. so, Doug is right and I'm w/ him when he though that shouldn't happen until this `feature' isn't fixed and arguing than UPDATING is the solution is too simple. this commit break some installation in a way it shouldn't. point. Cyrille. -- Cyrille Lefevre mailto:cyrille.lefevre@laposte.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message