From: Chris Wright <chrisw@osdl.org>
To: John M Collins <jmc@xisl.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Exploit in 2.6 kernels
Date: Tue, 12 Apr 2005 14:08:57 -0700 [thread overview]
Message-ID: <20050412210857.GT11199@shell0.pdx.osdl.net> (raw)
In-Reply-To: <1113318034.3105.46.camel@caveman.xisl.com>
* 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.
thanks,
-chris
next prev parent reply other threads:[~2005-04-12 21:50 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 [this message]
2005-04-12 21:32 ` John M Collins
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=20050412210857.GT11199@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=jmc@xisl.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.