From: Chris Wright <chrisw@osdl.org>
To: Frank Steiner <fsteiner-mail@bio.ifi.lmu.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Identify security-related patches
Date: Thu, 2 Sep 2004 11:48:07 -0700 [thread overview]
Message-ID: <20040902114807.G1973@build.pdx.osdl.net> (raw)
In-Reply-To: <4136C6E1.4090404@bio.ifi.lmu.de>; from fsteiner-mail@bio.ifi.lmu.de on Thu, Sep 02, 2004 at 09:08:17AM +0200
* Frank Steiner (fsteiner-mail@bio.ifi.lmu.de) wrote:
> is there an easy way to identify all security-related patches out of the
> mass of patches floating around on linux.bkbits.net or the kernel bugzilla?
No, there's not. It's not as simple as it seems. Your best bet is
monitoring vendor updates, as they have the same goal. Occasionaly
things get applied with a CVE candidate number (CAN-YYYY-NNNN), and
those are security relevant.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2004-09-02 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 7:08 Frank Steiner
2004-09-02 18:48 ` Chris Wright [this message]
2004-09-02 19:12 ` Valdis.Kletnieks
2004-09-02 20:22 ` Florian Weimer
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=20040902114807.G1973@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=fsteiner-mail@bio.ifi.lmu.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
all inboxes | Powered by JetHome®