From owner-freebsd-hackers  Fri Oct 24 19:03:47 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id TAA05147
          for hackers-outgoing; Fri, 24 Oct 1997 19:03:47 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA05142
          for <hackers@FreeBSD.ORG>; Fri, 24 Oct 1997 19:03:45 -0700 (PDT)
          (envelope-from jkh@time.cdrom.com)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id TAA13382; Fri, 24 Oct 1997 19:03:09 -0700 (PDT)
To: Alfred Perlstein <perlsta@cs.sunyit.edu>
cc: hackers@FreeBSD.ORG
Subject: Re: why is freebsd distributed like this? 
In-reply-to: Your message of "Fri, 24 Oct 1997 21:54:11 CDT."
             <Pine.BSF.3.96.971024215119.6289B-100000@server.local.sunyit.edu> 
Date: Fri, 24 Oct 1997 19:03:09 -0700
Message-ID: <13379.877744989@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Why are there releases floating around with security holes in them?
> certain 'fixes' that are trivial but nessesary like the procfs patch
> should be applied all around the source tree as soon as possible.

1. We can't change what's already been released, at least not without
   causing serious confusion.

2. If you know of a specific security hole still in -current or -stable
   then the thing to do is NOT to whine here about it, the thing to do
   is to submit a PR if you're actually interested in seeing it fixed.

And it's as simple as that.

				Jordan