From: John M Collins <jmc@xisl.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Exploit in 2.6 kernels
Date: Tue, 12 Apr 2005 22:32:59 +0100 [thread overview]
Message-ID: <1113341579.3105.63.camel@caveman.xisl.com> (raw)
In-Reply-To: <20050412210857.GT11199@shell0.pdx.osdl.net>
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.
(Or is there a sneaky way of patching the modules so they'll work in
another kernel without tainting it?).
John Collins Xi Software Ltd www.xisl.com Tel: +44 (0)1707 886110
(Direct) +44 (0)7799 113162 (Mobile)
next prev parent reply other threads:[~2005-04-12 21:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 9:34 Exploit in 2.6 kernels John M Collins
2005-04-12 12:24 ` Baruch Even
2005-04-12 15:00 ` John M Collins
2005-04-12 21:08 ` Chris Wright
2005-04-12 21:32 ` John M Collins [this message]
2005-04-13 5:28 ` Valdis.Kletnieks
2005-04-13 9:47 ` Helge Hafting
2005-04-13 12:59 ` Lennart Sorensen
2005-04-13 13:06 ` Lars Marowsky-Bree
2005-04-13 13:23 ` Lennart Sorensen
2005-04-13 14:01 ` John M Collins
2005-04-16 2:32 ` Adrian Bunk
2005-04-13 15:22 ` Chris Friesen
2005-04-14 14:01 ` Helge Hafting
2005-04-20 18:17 ` nVidia stuff again Doug Ledford
2005-04-20 23:12 ` Dave Airlie
2005-04-21 11:23 ` Helge Hafting
2005-04-21 12:15 ` Doug Ledford
2005-04-21 12:54 ` Dave Airlie
2005-04-21 13:35 ` Lennart Sorensen
2005-04-21 14:43 ` Manu Abraham
2005-04-21 21:17 ` J.A. Magallon
2005-04-22 14:44 ` Arjan van de Ven
2005-04-15 15:00 ` Exploit in 2.6 kernels Alan Cox
2005-04-15 16:06 ` Dave Airlie
2005-04-15 16:19 ` Duncan Sands
2005-04-14 12:46 ` Helge Hafting
2005-05-05 22:00 ` Olaf Titz
2005-04-13 13:02 ` Lennart Sorensen
2005-04-13 14:26 ` Eric Rannaud
2005-04-13 14:41 ` Lennart Sorensen
2005-04-14 20:02 ` Greg Folkert
2005-04-14 22:27 ` John M Collins
2005-05-09 18:37 ` Alessandro Salvatori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1113341579.3105.63.camel@caveman.xisl.com \
--to=jmc@xisl.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox