From: Adrian Bunk <bunk@stusta.de>
To: Ingo Oeser <ioe-lkml@rameria.de>
Cc: Chris Wright <chrisw@sous-sol.org>,
Maciej Soltysiak <solt2@dns.toxicfilms.tv>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.16.16
Date: Sat, 13 May 2006 17:56:10 +0200 [thread overview]
Message-ID: <20060513155610.GB6931@stusta.de> (raw)
In-Reply-To: <200605131735.20062.ioe-lkml@rameria.de>
On Sat, May 13, 2006 at 05:35:19PM +0200, Ingo Oeser wrote:
> Hi Chris,
>
> first of all: Thanks for the good work!
>
> On Thursday, 11. May 2006 19:33, Chris Wright wrote:
> > Assigning any official severity is a bit of a slippery slope, but
> > making sure it's clear what type of issue (i.e. local DoS in this case)
> > is very reasonable.
>
> Yes, I agree.
>
> I would like to know:
> - local or remote exploitable
> - if a DoS: hang, only service failure, major slowdown
> - privilege escalation possiible and how far (valid user, root, kernel-level)
> - required privileges (root or user)
>
> That would help risk management a lot :-)
>
> If you have a lot of time: Affected software components, but these can
> be taken from the patches/commit info or CVE.
The CVE should be enough for easily getting all information you
requested.
Information whether it's a DoS or a root exploit is helpful, but any
qualified person doing risk management will anyways lookup the CVE.
> Thanks & Regards
>
> Ingo Oeser
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-05-13 15:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 2:25 Linux 2.6.16.16 Chris Wright
2006-05-11 2:29 ` Chris Wright
2006-05-11 10:34 ` Maciej Soltysiak
2006-05-11 11:07 ` Nick Warne
2006-05-11 16:50 ` Daniel Barkalow
2006-05-11 17:33 ` Chris Wright
2006-05-11 18:03 ` BUG: soft lockup detected on CPU#0! Winn Johnston
2006-05-12 15:51 ` Winn Johnston
2006-05-13 15:35 ` Linux 2.6.16.16 Ingo Oeser
2006-05-13 15:56 ` Adrian Bunk [this message]
2006-05-13 17:29 ` Nick Warne
2006-05-14 3:59 ` Greg KH
2006-05-14 5:17 ` Willy Tarreau
2006-05-15 17:57 ` Chris Wright
2006-05-14 7:46 ` Maciej Soltysiak
2006-05-15 16:30 ` Greg KH
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=20060513155610.GB6931@stusta.de \
--to=bunk@stusta.de \
--cc=chrisw@sous-sol.org \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=solt2@dns.toxicfilms.tv \
/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.