atom feed22 messages in org.freebsd.freebsd-securityRe: FreeBSD Security Advisory FreeBSD...
FromSent OnAttachments
FreeBSD Security AdvisoriesJul 10, 2001 7:01 am 
Mike TancsaJul 10, 2001 7:04 am 
Mike TancsaJul 10, 2001 9:24 am 
Jason DiCioccioJul 10, 2001 9:27 am 
Jason DiCioccioJul 10, 2001 9:39 am 
Alex PopaJul 10, 2001 1:46 pm 
Przemyslaw FrasunekJul 10, 2001 2:09 pm 
Alex PopaJul 10, 2001 2:09 pm 
Christopher SchulteJul 10, 2001 2:15 pm 
bowJul 10, 2001 3:14 pm 
Joe OliveiroJul 10, 2001 3:18 pm 
Domas MituzasJul 10, 2001 3:44 pm 
Dima DorfmanJul 10, 2001 6:59 pm 
Jacques A. VidrineJul 11, 2001 8:45 am 
Kris KennawayJul 11, 2001 11:44 am 
Kris KennawayJul 11, 2001 12:05 pm 
Kris KennawayJul 11, 2001 12:18 pm 
Kris KennawayJul 11, 2001 12:21 pm 
Jacques A. VidrineJul 11, 2001 12:29 pm 
Kris KennawayJul 11, 2001 12:32 pm 
Dima DorfmanJul 11, 2001 3:48 pm 
Kris KennawayJul 11, 2001 3:58 pm 
Subject:Re: FreeBSD Security Advisory FreeBSD-SA-01:
From:Jacques A. Vidrine (n@nectar.com)
Date:Jul 11, 2001 8:45:47 am
List:org.freebsd.freebsd-security

On Tue, Jul 10, 2001 at 06:59:57PM -0700, Dima Dorfman wrote:

Jason DiCioccio <jdic@epylon.com> 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,

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message