Date: Wed, 23 Oct 2002 12:36:40 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Steven Ames <steve@virtual-voodoo.com> Cc: Andrew Mishchenko <andrew@driftin.net>, freebsd-current@FreeBSD.ORG Subject: Re: Request: remove ssh1 fallback Message-ID: <3DB6FA48.896CB7EA@mindspring.com> References: <007501c27a5c$27203fc0$6501a8c0@VAIO650> <20021023155753.GB7503@HAL9000.homeunix.com> <004401c27aad$740a5400$33d90c42@officescape.net> <20021023161643.GA7813@HAL9000.homeunix.com> <20021023143917.GA3222@driftin.net> <3DB6F2E1.799FF6F7@mindspring.com> <009001c27ac8$af6d77f0$33d90c42@officescape.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Steven Ames wrote: > From: "Terry Lambert" <tlambert2@mindspring.com> > > So I upgrade, and I can't get back into the box from my SSH1 > > client machine to reenable SSH1 services on the box. Genius! > > 8-) 8-). > > Its somewhat less than genious not to look over any new config > files you've installed to make sure they do what you expect. That's > blind trust. Not genius. A genius may have read the UPDATING > file and been forwarned :) No, a genius would have set up the upgrade software to interactively question the user about whether they wanted to leave that facility enabled, based on the upgrade software's understanding that the upgrade process would in fact disable features, and if there was a moral equivalent to "upgrade -y", then everything that was enabled would be left enabled, even if that meant adding command line options into the rc.conf entry for the sshd arguments. Do Not Change Behaviour On Upgrade Without Eplicit User Approval(tm). -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DB6FA48.896CB7EA>