Re: Exploit in 2.6 kernels

Helge Hafting
2005-04-13T09:44:00Z

John M Collins wrote:

>On Tue, 2005-04-12 at 14:08 -0700, Chris Wright wrote:
>
>
>>* John M Collins (jmc@xisl.com) wrote:
>>
>>
>>>Thanks to everyone for the pointers on this one I've rebuilt the kernels
>>>and we'll see what happens.
>>>
>>>
>>BTW, I'd recommend updating to 2.6.11.7 so that you're protected from
>>another local root exploit.
>>
>>
>
>I'll do that - trouble is round where I am they dish out Nvidia cards
>like confetti, I've got them in the machine I use most and another 2 and
>you have to do all that gyrating with running the script to FTP down and
>build the secret module before you can run X. This is a big disincentive
>when it comes to installing new kernels.
>
>I wish some kind soul would speak nicely to Nvidia and get them to see
>reason on the point but I suspect I'm not the first person to wish that.
>
>
You're not. Complain to nvidia - using both email and snailmail.
If everybody with such problems did that, chances are they see
the light someday. Oh, and complain to the guy handing out
nvidia cards like confetti, state your preference for some other
card. Perhaps that is easier to achieve.

>(Or is there a sneaky way of patching the modules so they'll work in
>another kernel without tainting it?).
>
>
Whats wrong with tainting? It is just a message, telling you that
the kernel is unsupported. In this case because you're running a
closed-source module. The tainting message itself does not do
anything bad. There is a way - which is to write an open nvidia
driver. To do that, you'll need to get the specs out of nvidia or
figure it out by reverse-engineering some other nvidia driver. Either
approach is hard, so people generally find it cheaper to just buy
a supported card.

Helge Hafting