Date: Sun, 07 Jul 2002 20:06:15 -0500 From: "F. Even" <freebsdlists@elitists.org> To: <security@FreeBSD.ORG> Subject: Re: Default ssh protocol in -STABLE [was: Message-ID: <B94E4FB7.1055E%freebsdlists@elitists.org> In-Reply-To: <bulk.44049.20020707115036@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Really? I seem to have noticed the introduction of a "periodic.conf" between 4.0 and 4.4. While it was pleasant to see it, it was still a change. This seems about the same....a small config change, except the default is a little different...and if people are blindly upgrading entire systems following the STABLE branch...well.... If I'm understanding right, this change is not going to be introduced into "RELENG_4_ver," just the STABLE branch. It would seem to me that you would know if you are upgrading your version of OpenSSH, the main way to connect to your machine remotely, and you should be familiar enough to know the defaults is different, and to either change it back or not. I mean....if you are taking the time to upgrade, a config file setting shouldn't be that big of a deal. Frank On 7/7/02 1:50 PM, "security-digest" <owner-freebsd-security-digest@FreeBSD.ORG> wrote: > Date: Sat, 06 Jul 2002 22:42:29 -0700 > From: Doug Barton <DougB@FreeBSD.org> > Subject: Re: Default ssh protocol in -STABLE [was: HEADS UP: > FreeBSD-STABLEnowhas OpenSSH 3.4p1] > > Anthony Rubin wrote: >> >> In order for this change to affect a user they would have to run >> mergemaster, see the change, and tell mergemaster to go ahead and merge >> or overwrite their config file. > > Or, install a new box after wiping the old layout, or any number of > scenarios. The point remains, we don't do changes like this within a > - -stable branch. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B94E4FB7.1055E%freebsdlists>