thoughts on kernel security issues
Where is 2.6.10.1 with the security fix only ?
I have not yet finished to deal with the TCP troubles moving to 2.6.10 generated on my production server, and now, I should apply another large set of mainly untested patches just to fill the security hole. This just cannot be done in a fiew days because on many organisations, the new kernel has to pass several days on secondary servers before reaching the main ones.
Now assuming that I have other production servers still running older kernels, I have no way to get the simple fix from kernel.org and backport it to 2.6.8 and 2.6.9, unless I'm a kernel fulltime worker that reads all messages on kernel mailing list.
Basically, you are currently leaving non distribution related users alone in the cold and this is really really bad for the confidence we have in Linux, so please publish a 2.6.10.1 with the short term solution to fix the hole. Of course this does not prevent to publish 2.6.10.2 when you found a better solution, or use a different fix in 2.6.11 since they are not based on 2.6.10.1
Regards,
Hubert Tonneau
PS: I believe that it would also be a very good idea, since Linux is now expected to be a mature organisation, to automatically publish 2.6.x.y new holes only fix patch for each stable kernel that has been released less than a year ago. This would enable smoother upgrade of highly important production servers.
Quoted 5 lines · * Hubert Tonneau ([email protected]) wrote:
Basically, you are currently leaving non distribution related users alone in the cold and this is really really bad for the confidence we have in Linux, so please publish a 2.6.10.1 with the short term solution to fix the hole. Of course this does not prevent to publish 2.6.10.2 when you found a better solution, or use a different fix in 2.6.11 since they are not based on 2.6.10.1
I agree (it was part of my original mail), and would like to remedy this. For now, you can pick up fixes from -ac tree.
Quoted 8 lines
Regards,
Hubert TonneauPS: I believe that it would also be a very good idea, since Linux is now expected to be a mature organisation, to automatically publish 2.6.x.y new holes only fix patch for each stable kernel that has been released less than a year ago. This would enable smoother upgrade of highly important production servers.
Not sure about that (it's quite some work), but at least the _current_ stable release version.
thanks,
-chris
Signature · 1 line
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net