-   Slackware (
-   -   Slack 10.2's default 2.4.31 kernel - how do I security patch it? (

Old_Fogie 08-07-2006 06:24 AM

Slack 10.2's default 2.4.31 kernel - how do I security patch it?
Hi all,

I've noticed throughout my time here that some people mention that there are "security" fixes/patches for the stock 2.4.31 IDE Generic kernel.

I went through the security notices pages for both 2005/2006 at Slackware's site, and I don't see anything listed there for kerenel.

Can someone please point me to where this advisory is, and/or where I can get Pat's fix for it?

Thank you.

Alien Bob 08-07-2006 06:35 AM

The kernel is not taken into account when fixing security issues. Slackware has always come with (near) pristine unpatched kernels. I don't even know if old kernels get fixed and patched by the kernel team.

I guess you should install one of the recent 2.4 kernels from source (using the .config file from your running kernel as a template to jumpstart the source configuration process) if you are concerned with your current kernel's secirity level.


masonm 08-07-2006 06:46 AM

Honestly if you're going to compile a new kernel anyway I'd go with a new 2.6 series kernel as you get a bit snappier kernel with a good deal better hardware support.

Old_Fogie 08-07-2006 11:10 AM

Ok ty gent's.

I was just "fearful" as I see some people make statements that the kernel 2.4.31 is 'in-secure' at this time. That comment is somewhere in the mega-thread for the next slackware.

Ok, I'll slap in another kernel for just in case of reasons, I have the drive space.

But it is good for me to hear/know that I am responsible to check for security patches to my slackware kernels and not leave it to Pat.

I was not aware of that. I had assumed that since other distor's (like opensuse for example) issue security patched kernels when they arise.

Definitely a good learning point here thanks again.

All times are GMT -5. The time now is 05:16 PM.