[kernel-sec-discuss] r1857 - active retired
Michael Gilbert
michael.s.gilbert at gmail.com
Wed Jun 23 15:00:43 UTC 2010
On Wed, 23 Jun 2010 16:54:36 +0200, Moritz Muehlenhoff wrote:
> On Wed, Jun 23, 2010 at 10:46:38AM -0400, Michael Gilbert wrote:
> > On Wed, 23 Jun 2010 16:32:42 +0200, Moritz Muehlenhoff wrote:
> > > On Tue, Jun 22, 2010 at 06:10:30PM +0000, Michael Gilbert wrote:
> > > > Author: gilbert-guest
> > > > Date: 2010-06-22 18:10:26 +0000 (Tue, 22 Jun 2010)
> > > > New Revision: 1857
> > > >
> > > > Added:
> > > > retired/CVE-2010-1148
> > > > retired/CVE-2010-1173
> > > > retired/CVE-2010-1187
> > > > Removed:
> > > > active/CVE-2010-1148
> > > > active/CVE-2010-1173
> > > > active/CVE-2010-1187
> > > > Log:
> > > > retire some issues
> > >
> > > Please keep them in active; they're still unfixed in 2.6.32.x stable
> >
> > all of debian's supported kernels are fixed, so from that perspective,
> > the issues are done. isn't that what kernel-sec tracks? or is someone
> > using this info to coordinate pushes to the linux-stable tree?
>
> Yes, that would be me :-)
>
> > if so,
> > then i agree that from that perspective they aren't really done. i
> > haven't seen evidence of anyone doing this, but if they are that's
> > great.
>
> Greg Kroah-Hartman usually get CCed on most security-relevant bugs,
> but I'm checking the status every few weeks to keep 2.6.32.x up-to-date.
ok, good to hear. i'll make sure to leave these kinds of cases in
active from now on. thanks for your work on that!
mike
More information about the kernel-sec-discuss
mailing list