From: "Barry K. Nathan" <barryn@pobox.com>
To: linux-os@analogic.com
Cc: Steve Bergman <steve@rueb.com>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Proper procedure for reporting possible security vulnerabilities?
Date: Mon, 10 Jan 2005 16:44:09 -0800 [thread overview]
Message-ID: <20050111004409.GB4378@ip68-4-98-123.oc.oc.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0501101707220.14001@chaos.analogic.com>
On Mon, Jan 10, 2005 at 05:09:18PM -0500, linux-os wrote:
> Are you sure it's an exploit? My information was that grsecurity
> wanted some of their 'hooks' added to recent kernels and it hasn't
> happened. That's not a security problem, that's an application
> problem.
Yes, exploit (although the severity is arguable). See the 2.6.10-ac7
portion of the changelog here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=110523047925271&w=2
-Barry K. Nathan <barryn@pobox.com>
next prev parent reply other threads:[~2005-01-11 2:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 16:46 Proper procedure for reporting possible security vulnerabilities? Steve Bergman
2005-01-10 18:23 ` Indrek Kruusa
2005-01-10 19:24 ` Alan Cox
2005-01-11 9:32 ` Florian Weimer
2005-01-10 21:31 ` Florian Weimer
2005-01-10 21:42 ` Steve Bergman
2005-01-10 22:08 ` Diego Calleja
2005-01-11 0:19 ` Barry K. Nathan
2005-01-11 0:45 ` Diego Calleja
2005-01-11 9:35 ` Florian Weimer
2005-01-11 16:57 ` Jesper Juhl
2005-01-11 17:05 ` Jan Engelhardt
2005-01-10 22:09 ` linux-os
2005-01-11 0:44 ` Barry K. Nathan [this message]
2005-01-10 22:11 ` Jesper Juhl
2005-01-11 0:40 ` Chris Wright
2005-01-11 1:09 ` Diego Calleja
2005-01-11 1:18 ` Chris Wright
2005-01-11 17:05 ` Jesper Juhl
2005-01-11 16:39 ` Alan Cox
2005-01-11 21:25 ` Jesper Juhl
2005-01-11 21:29 ` Chris Wright
2005-01-12 21:05 ` Jesper Juhl
2005-01-17 22:49 ` Werner Almesberger
2005-01-17 22:52 ` Chris Wright
2005-01-17 23:23 ` Christoph Hellwig
2005-01-17 23:26 ` Chris Wright
2005-01-17 23:57 ` Alan Cox
2005-01-18 1:08 ` Chris Wright
2005-01-11 17:57 ` Chris Wright
2005-01-12 12:23 ` Florian Weimer
2005-01-11 9:49 ` Florian Weimer
2005-01-11 16:10 ` Alan Cox
2005-01-12 12:33 ` Florian Weimer
2005-01-13 15:36 ` Alan Cox
[not found] <200501101959.j0AJxUvl032294@laptop11.inf.utfsm.cl>
2005-01-10 21:36 ` Indrek Kruusa
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=20050111004409.GB4378@ip68-4-98-123.oc.oc.cox.net \
--to=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=steve@rueb.com \
/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;
as well as URLs for NNTP newsgroup(s).