From: Daniel Drake <dsd@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: [gentoo-kernel] More manpower needed for Gentoo Kernel Security project
Date: Sun, 20 May 2007 16:03:45 -0400 [thread overview]
Message-ID: <4650A9A1.90202@gentoo.org> (raw)
Anyone interested in contributing the Gentoo kernel security project?
Basic roles here are to handle vulnerabilities (both minor and major) in
the kernel. The issues come in from databases such as cve.mitre.org,
usually with patches, and you have to coordinate those patches flowing
into the portage tree.
The usual process is to have a bug on the Gentoo bugzilla per security
report. Initially you get me to include the patch in genpatches, then
you CC maintainers of all other affected kernels and pester them until
they have fixed their kernel, either by including the newer genpatches
or by adding the patch individually.
This isn't a terribly interesting task, but is important and we're
behind on issue tracking here. The thing that will make it interesting
is that after getting a grasp of how the system works, we are looking
for someone to develop software to help us track the security bugs and
help communicate that info to users (who typically want to know when a
new kernel fixes a security issue, so that they can upgrade). This
software would probably be web-based.
Anyone interested?
http://www.gentoo.org/proj/en/security/kernel.xml
Thanks,
Daniel
--
gentoo-kernel@gentoo.org mailing list
next reply other threads:[~2007-05-20 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 20:03 Daniel Drake [this message]
2007-05-20 20:53 ` [gentoo-kernel] Re: More manpower needed for Gentoo Kernel Security project Christian Heim
2007-05-21 10:03 ` [gentoo-kernel] " Charles Clément
2007-05-21 11:45 ` Robert Clark
2007-05-21 13:25 ` Strake
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=4650A9A1.90202@gentoo.org \
--to=dsd@gentoo.org \
--cc=gentoo-kernel@lists.gentoo.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