you mean all two of them and the least relevant ones at that? ;)
> the omission of that one is likely an oversight.
you mean after exploits have been out in the public, hit /. and others. do you realize that this bug is one of the most serious ones in a long time, affecting probably a decade's worth of kernels?
> Really, you should stop assuming bad faith on the part of the kernel devs.
who said i was assuming anything? the facts speak for themselves and i will continue to point them out whether you like it or not.
Posted Nov 10, 2009 23:05 UTC (Tue) by flewellyn (subscriber, #5047)
[Link]
What do you want them to do, then?
Stable kernels 2.6.31.6 and 2.6.27.39 released
Posted Nov 11, 2009 14:58 UTC (Wed) by drag (subscriber, #31333)
[Link]
Probably mention serious security fixes better so that people like I don't
have to wait for PaXTeam to point out issues like this one. :)
I mean; wouldn't it be nice to be able to trust what the kernel releases
changelogs say? Because right now you can't and not everybody is going to
understand the extent of a problem just because the logs reference a null
pointer.