From owner-freebsd-questions Wed Aug 13 07:39:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA20352 for questions-outgoing; Wed, 13 Aug 1997 07:39:17 -0700 (PDT) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA20347 for ; Wed, 13 Aug 1997 07:39:14 -0700 (PDT) Received: from localhost (spork@localhost) by super-g.inch.com (8.8.5/8.8.5) with SMTP id KAA06342 for ; Wed, 13 Aug 1997 10:37:56 -0400 (EDT) Date: Wed, 13 Aug 1997 10:37:55 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: questions@freebsd.org Subject: Security Fixes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What is the best way to determine whether a security fix has been committed to the -stable source tree? I specifically am curious about the rfork and procfs bugs and whether I should continue using local patches from this and other mailing lists or whether the cvsup I just completed took care of all this for me... Actually, digging through the cvsweb, I was able to see the procfs change committed yesterday, but I'm stumped on where to look for the rfork problem, as the patch I have is an LKM... Thanks, Charles