[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130220025039.GA32551@kroah.com>
Date: Tue, 19 Feb 2013 18:50:39 -0800
From: Greg KH <greg@...ah.com>
To: oss-security@...ts.openwall.com
Subject: Re: Linux kernel race condition with PTRACE_SETREGS
(CVE-2013-0871)
On Tue, Feb 19, 2013 at 05:47:23PM -0800, Greg KH wrote:
> On Tue, Feb 19, 2013 at 12:40:50PM -0800, Julien Tinnes wrote:
> > On Sat, Feb 16, 2013 at 2:49 AM, Solar Designer <solar@...nwall.com> wrote:
> > > The mainline commits from January are by Oleg Nesterov of Red Hat. Why
> > > wasn't(?) the issue handled with due severity within Red Hat, then -
> > > such that Red Hat would at the very least have a statement on whether
> > > and which of their kernels are affected by now. My guess is that the
> > > full severity of the issue might not have been understood by Oleg at the
> > > time, but it's only a guess.
> >
> > That's the eternal debate :) Since upstream doesn't want to handle
> > security and disclosure, I sure wish that distro vendors could
> > regroup, step-up and do it.
>
> I know some people don't "like" how the kernel team handles bug reports
> and fixes, but seriously, this should have been pretty obvious by anyone
> watching the stable kernel releases, which all distros do. The fact
> that the distros didn't notify others is not the kernel community's
> fault, sorry.
Ick, my appologies Julien, it seems we are in violent agreement here
about the role that distros should be playing. Sorry about that.
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.
