Date: Wed, 23 Oct 2002 12:56:55 -0700 From: Terry Lambert <tlambert2@mindspring.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Steven Ames <steve@virtual-voodoo.com>, Andrew Mishchenko <andrew@driftin.net>, freebsd-current@FreeBSD.ORG Subject: Re: Request: remove ssh1 fallback Message-ID: <3DB6FF07.5DAC9CCB@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> <20021023123349.A9132@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis wrote: > I think it's safe to say that if you do a remote upgrade to 5.0 and > miss this change (if it happens), you're probably going to have missed > several other more important change. A source upgrade from 4.x to 5.x > is definatly not for the faint of heart or the non detail oriented. I'm talking a binary upgrade, using the sysinstall "upgrade" option. Check the mailing list archives around 4.3-RELEASE, when it was discovered that /etc/pam.conf didn't get "ssh" lines added to it on upgrades, and people were getting locked out of boxes left and right (predates "other" entries). Changing behaviour on an upgrade, without the user's consent, is a bad thing (note: *consent*, not *knowledge*: it's not up to the user to know about everything some programmer has diddled into non-operability in the two years since FreeBSD 5.x was branched). -- 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?3DB6FF07.5DAC9CCB>