Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130227191705.GB21286@kroah.com>
Date: Wed, 27 Feb 2013 11:17:05 -0800
From: Greg KH <greg@...ah.com>
To: oss-security@...ts.openwall.com
Subject: Re: CVE request - Linux kernel: VFAT slab-based
 buffer overflow

On Wed, Feb 27, 2013 at 08:06:18PM +0100, Jason A. Donenfeld wrote:
> On Wed, Feb 27, 2013 at 5:17 PM, Greg KH <greg@...ah.com> wrote:
> > Every single patch we make to the kernel is public, it is up to you to
> > determine if you feel it is a "security fix" or not.  And to do so is a
> > non-trivial task, something that I sure don't want to be responsible for
> > trying to do.  And since no one else has ever stepped up to want to do
> > it either, there's not much more that can be done.
> >
> > Are you willing to do it?
> >
> 
> Yes! Sign me up, I volunteer. I'd be happy to watch the coordination
> between security@ and the git repo, and sent oss-sec an email when
> they align. Pencil me in.

No, I'm saying you need to watch the public commits, not the security@
traffic (which is very low), as that is where the huge majority of fixes
are made.

See my other responses about how the members of security@ are going to
notify the linux-distros list, not oss-sec.

greg k-h

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.