Date: Wed, 23 Oct 2002 15:01:51 -0500 From: "David W. Chapman Jr." <dwcjr@inethouston.net> To: Terry Lambert <tlambert2@mindspring.com> Cc: Brooks Davis <brooks@one-eyed-alien.net>, Steven Ames <steve@virtual-voodoo.com>, Andrew Mishchenko <andrew@driftin.net>, freebsd-current@FreeBSD.ORG Subject: Re: Request: remove ssh1 fallback Message-ID: <20021023200151.GA42945@leviathan.inethouston.net> In-Reply-To: <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> <3DB6FF07.5DAC9CCB@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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). Isn't that what UPDATING is for and wouldn't between 4.x and 5.x be better than 5.x and 5.x+n? -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. <www.inethouston.net> dwcjr@freebsd.org FreeBSD Committer <www.FreeBSD.org> 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?20021023200151.GA42945>