Date: Wed, 14 Mar 2001 18:49:53 +0000 From: Paul Richards <paul@freebsd-services.co.uk> To: Jordan Hubbard <jkh@osd.bsdi.com> Cc: kris@obsecurity.org, gsutter@zer0.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: proposals for fixing the PROBLEM at hand Message-ID: <3AAFBD51.A77E97A1@freebsd-services.co.uk> References: <20010314005648.I9369@klapaucius.zer0.org> <20010314011016.A28290@mollari.cthul.hu> <3AAF86A6.65492AEC@freebsd-services.co.uk> <20010314102240A.jkh@osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jordan Hubbard wrote: > > > Well I was under the impression that you were going to be quite pedantic > > about it being security fixes only. If it's critical bugfixes as well > > then that's exactly what I've been calling for. > > They would have to be so critical as to constitute something like a > panic() which joe user could induce by running a common command, > arguably a DoS anyway and something back in the security category. > You're not going to get your "has all the necessary updates, runs > all the latest software" goal out of this at all and you'll still > need to act like a real admin. :) Not really, this is exactly what I've always advocated, a branch that has critical patches applied, that can be tracked in production environments without risking any incompatibilities ensuing. The issue of whether ports will support the -RELEASE branch is a separate one. Paul. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3AAFBD51.A77E97A1>