26 Sep 2010 12:31
Kernel Security Update Target Delay?
Richard Freeman <rich0 <at> gentoo.org>
2010-09-26 10:31:47 GMT
2010-09-26 10:31:47 GMT
Gentoo has been vulnerable to a highly-publicized (Guardian, Slashdot, the works) local privilege escalation for almost two weeks now. (Well, it has been vulnerable for years, but of course we didn't know about it until two weeks ago.) In the bugzilla thread tracking the problem it has been mentioned a few times that the kernel does not receive GLSA support: http://bugs.gentoo.org/show_bug.cgi?id=337645 Looking at the security webpage, it seems to me that while we don't PUBLISH GLSAs for the kernel, the intent is to still fix problems (to do otherwise would seem quite insane). Looking at the normal GLSA process, this would rate as a A1 criticality problem (local escalation in a system component), with a target resolution of 3 days. We're going on 10 days now on bug 337645 with no mention of even targeting any particular release for stabilization. Obviously the current bug will get done when it gets done, and it isn't any skin off my back as I've upgraded (and in the likely event that 34-r10 gets called for stable I can keyword it without further testing). However, for the longer term it seems like something needs to change in the process. I don't see how kernel vulnerabilities can sit around for days. Most distros pushed out patches to stable users same-day or within a day or two. Perhaps a mitigating solution might be to open a security bug as soon as Gentoo hears about a problem, and notify the package maintainers. Then the maintainers must either call for stabilization within 48 hours, or publish a plan for how they will get the fix stabilized within the(Continue reading)
RSS Feed