From owner-freebsd-current Wed Oct 23 13:52:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDDA037B401 for ; Wed, 23 Oct 2002 13:52:36 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 940E543E3B for ; Wed, 23 Oct 2002 13:52:36 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 66239 invoked by uid 1000); 23 Oct 2002 20:52:37 -0000 Date: Wed, 23 Oct 2002 13:52:37 -0700 (PDT) From: Nate Lawson To: Andrew Mishchenko Cc: freebsd-current@freebsd.org Subject: Re: Request: remove ssh1 fallback In-Reply-To: <20021023163016.GA3462@driftin.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Wed, 23 Oct 2002, Andrew Mishchenko wrote: > On Wed 23 Oct, Terry Lambert wrote: > > What if the client machine is a SSH1 Solaris (or Windows) box > > going into a FreeBSD rackmount? > > > > It should *at least* be available as a command line option to > > the daemon; since some boxes *don't have* consoles at all, it > > would have the same effect of turning them into a doorstop to > > disable this flag, once it's available, by default (right now, > > it just provides both). > > What could be done with reasonable safety is leave current configs > as they are, not changing anything for people upgrading, but setting > the default behavior for default installs to no SSH1. > > Andrew I heard of something like that before. Oh yeah, mergemaster(8). -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message