From: Chris Wright <chrisw@osdl.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.11.10
Date: Mon, 16 May 2005 14:11:56 -0700 [thread overview]
Message-ID: <20050516211156.GE23013@shell0.pdx.osdl.net> (raw)
In-Reply-To: <87sm0mx50e.fsf@deneb.enyo.de>
* Florian Weimer (fw@deneb.enyo.de) wrote:
> * Greg KH:
>
> > Due to a recently announced security issue with the current kernel, we
> > (the -stable team) are announcing the release of the 2.6.11.10 kernel.
>
> Would it be possible to cross-reference the vulnerabilities in a
> precise manner, maybe using CVE names?
The ChangeLog has this info (CVE CAN-2005-1264).
http://kernel.org/git/gitweb.cgi?p=linux%2Fkernel%2Fgit%2Fgregkh%2Flinux-2.6.11.y.git;a=log
But, it's reasonble to ask for these in announce email, thanks.
-chris
next prev parent reply other threads:[~2005-05-16 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 18:25 Linux 2.6.11.10 Greg KH
2005-05-16 18:26 ` Greg KH
2005-05-16 19:52 ` Dave Jones
2005-05-16 20:58 ` Florian Weimer
2005-05-16 21:11 ` Chris Wright [this message]
2005-05-16 22:15 ` 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=20050516211156.GE23013@shell0.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=fw@deneb.enyo.de \
--cc=gregkh@suse.de \
--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