From: Eugene Teo <eugeneteo@kernel.org>
To: linux-kernel@vger.kernel.org, Eugene Teo <eugeneteo@kernel.org>
Subject: CVE tagged Linux kernel git repositories
Date: Thu, 02 Dec 2010 10:18:22 +0800 [thread overview]
Message-ID: <4CF701EE.7090201@kernel.org> (raw)
Hi,
I have published CVE tagged Linux kernel git repositories for 2.6,
2.6.32.y and 2.6.36.y. They are tagged with all the security issues
reported this year.
You can find them at http://git.kernel.org or
http://git.kernel.org/?p=linux/kernel/git/eugeneteo/linux-2.6-cve-tagged.git;a=summary
http://git.kernel.org/?p=linux/kernel/git/eugeneteo/linux-2.6.32.y-cve-tagged.git;a=summary
http://git.kernel.org/?p=linux/kernel/git/eugeneteo/linux-2.6.36.y-cve-tagged.git;a=summary
You can see when the security issues were addressed:
http://git.kernel.org/?p=linux/kernel/git/eugeneteo/linux-2.6-cve-tagged.git;a=tags
You can also search for security fixes by CVE names, e.g. CVE-2010-2943:
http://git.kernel.org/?p=linux/kernel/git/eugeneteo/linux-2.6-cve-tagged.git;a=shortlog;h=refs/tags/CVE-2010-2943
In this example, you will notice that there are two tags of the same CVE
name, CVE-2010-2943 and CVE-2010-2943.05. That means that there are five
patches for this CVE name, and you can access them via CVE-2010-2943.01
to .05.
Hope this is useful!
Thanks, Eugene
reply other threads:[~2010-12-02 2:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4CF701EE.7090201@kernel.org \
--to=eugeneteo@kernel.org \
--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