From: Ow Mun Heng <Ow.Mun.Heng@wdc.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Linux Kernel Warning
Date: Fri, 14 Jul 2006 14:44:20 -0700 [thread overview]
Message-ID: <1152913461.32378.31.camel@neuromancer.home.net> (raw)
In-Reply-To: <44B80B96.8040907@gentoo.org>
On Fri, 2006-07-14 at 14:24 -0700, Donnie Berkholz wrote:
> There's also
> the workaround mentioned in the SANS message if you don't feel
> comfortable with patching, as long as you don't need to use core dumps
> as non-root.
Besides that, there's also the fact that if you don't have local users,
then it's pretty safe.(Unless you get hacked for a 0-day or for not
doing glsa-checks)
My Take anyway.
(that and the workaround)
--
Ow Mun Heng <Ow.Mun.Heng@wdc.com>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-14 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-14 21:01 [gentoo-user] Linux Kernel Warning Timothy A. Holmes
2006-07-14 21:15 ` Richard Fish
2006-07-14 21:22 ` Raymond Lewis Rebbeck
2006-07-14 21:24 ` Donnie Berkholz
2006-07-14 21:44 ` Ow Mun Heng [this message]
2006-07-14 21:40 ` Daniel Drake
2006-07-14 22:59 ` Daniel Drake
-- strict thread matches above, loose matches on Subject: below --
2006-07-15 14:47 Timothy A. Holmes
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=1152913461.32378.31.camel@neuromancer.home.net \
--to=ow.mun.heng@wdc.com \
--cc=gentoo-user@lists.gentoo.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