From owner-freebsd-security Wed Jul 11 8:46:23 2001 Delivered-To: freebsd-security@freebsd.org Received: from gatekeeper.orem.verio.net (gatekeeper.orem.verio.net [192.41.0.8]) by hub.freebsd.org (Postfix) with ESMTP id 2570537B405; Wed, 11 Jul 2001 08:46:21 -0700 (PDT) (envelope-from nectar@nectar.com) Received: from proxy.dmz.orem.verio.net (proxy.dmz.orem.verio.net [10.1.1.11]) by gatekeeper.orem.verio.net (Postfix) with ESMTP id 084FD3BF107; Wed, 11 Jul 2001 09:46:21 -0600 (MDT) Received: from shade.nectar.com (unknown [10.99.128.122]) by proxy.dmz.orem.verio.net (Postfix) with ESMTP id BA3647C007; Wed, 11 Jul 2001 09:46:20 -0600 (MDT) Received: (from nectar@localhost) by shade.nectar.com (8.11.4/8.11.3) id f6BFk9900746; Wed, 11 Jul 2001 10:46:09 -0500 (CDT) (envelope-from nectar) Date: Wed, 11 Jul 2001 10:46:09 -0500 From: "Jacques A. Vidrine" To: Dima Dorfman Cc: Jason DiCioccio , "'security@freebsd.org'" , kris@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-01: Message-ID: <20010711104608.A600@shade.nectar.com> References: <657B20E93E93D4118F9700D0B73CE3EA02FFEFA1@goofy.epylon.lan> <20010711015958.0921D3E28@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010711015958.0921D3E28@bazooka.unixfreak.org>; from dima@unixfreak.org on Tue, Jul 10, 2001 at 06:59:57PM -0700 X-Url: http://www.nectar.com/ Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Jul 10, 2001 at 06:59:57PM -0700, Dima Dorfman wrote: > Jason DiCioccio writes: > > So then I'm guessing this has been 3.5-STABLE is not vulnerable? > > Just want to be sure :-) > > What makes you say that? The necessary fix isn't present in RELENG_3, > and I doubt that there's something else which hides the issue. I haven't double-checked, but it looks like this bug was enabled by revision 1.54 of src/sys/kern/kern_fork.c (allowing shared signal handlers with rfork). That would include 3.1-RELEASE and all following releases. Cheers, -- Jacques Vidrine / n@nectar.com / jvidrine@verio.net / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message