From: Tim Yamin <plasmaroo@gentoo.org>
To: gentoo-kernel@lists.gentoo.org
Subject: Re: [gentoo-kernel] Gentoo Kernel Security Policy (DRAFT)
Date: Thu, 16 Mar 2006 02:59:56 +0000 [thread overview]
Message-ID: <20060316025956.GA11554@toucan.gentoo.org> (raw)
In-Reply-To: <20060316004318.GA15855@kroah.com>
On Wed, Mar 15, 2006 at 04:43:18PM -0800, Greg KH wrote:
> On Wed, Mar 15, 2006 at 11:31:01PM +0000, John Mylchreest wrote:
> > 3. Genpatches-Base Support
> >
> > For as long as there is a kernel package in the tree using genpatches,
> > the corresponding genpatches-base will be maintained from a security
> > point of view. Announcements for each update follow the normal
> > procedure, however there is a caveat. Kernel sources which use
> > genpatches should not lapse more than 2 minor releases from upstream.
> > IE: kernel sources should not fall behind 2.6.14 if the most recent
> > upstream release is 2.6.16. In the extreme case where this is not
> > technically possible, this will require it being addressed on a
> > case-by-case basis, and a sectag penalty of 10 applied if appropriate.
>
> Wow, we are commiting to support 2 kernel versions back? Since when?
> That's going to be a major effort that no one has signed up to do (even
> kernel.org doesn't offer that...) Do we _really_ want to say we are
> going to do this?
>
> If so, we're already behind with all of the recent 2.6.15 security fixes
> not being backported to 2.6.14 :)
Only they are being backported... kerframil is helping out with that task.
--
gentoo-kernel@gentoo.org mailing list
next prev parent reply other threads:[~2006-03-16 3:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 23:31 [gentoo-kernel] Gentoo Kernel Security Policy (DRAFT) John Mylchreest
2006-03-15 23:42 ` Tim Yamin
2006-03-16 0:43 ` Greg KH
2006-03-16 2:59 ` Tim Yamin [this message]
2006-03-16 17:30 ` Greg KH
2006-03-18 10:41 ` John Mylchreest
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=20060316025956.GA11554@toucan.gentoo.org \
--to=plasmaroo@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