From owner-freebsd-security Sun May 21 23:25:47 2000 Delivered-To: freebsd-security@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 044A637B7C9 for ; Sun, 21 May 2000 23:25:43 -0700 (PDT) (envelope-from DougB@gorean.org) Received: from gorean.org (doug@master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id XAA19270; Sun, 21 May 2000 23:25:26 -0700 (PDT) (envelope-from DougB@gorean.org) Message-ID: <3928D2D5.DCA07289@gorean.org> Date: Sun, 21 May 2000 23:25:25 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.72 [en] (X11; U; FreeBSD 5.0-CURRENT-0508 i386) X-Accept-Language: en MIME-Version: 1.0 To: Brett Glass Cc: Warner Losh , cjclark@home.com, freebsd-security@FreeBSD.ORG Subject: Re: The procfs Hole in 2.2.8-STABLE? References: <20000521140847.G96573@cc942873-a.ewndsr1.nj.home.com> <4.3.1.2.20000521225733.048a0c40@localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brett Glass wrote: > > Hopefully, some of the things that are being fixed in 4.0 will > be backported to 3.5. Tradition (and at this point it's one that I agree with) says that only stability and security improvements get committed to the branches we're leaving behind after the most recent version branches. Adding new features to 3.x at this point would encourage people to stay with that branch. > We want 3.5 to be the "golden" release that > we use for production until 4.2 is ready and stable. Yes Brett, we're all well aware of what you want, you've stated it many times. However most of the project would prefer to help dispel the idea that the 4.x release isn't ready for production. That doesn't mean that you can't use whatever policy you want where you work, it just means that you don't need to tell us about it anymore. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message