public inbox for gentoo-security@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Eduardo Tongson" <propolice@gmail.com>
To: gentoo-security@lists.gentoo.org
Subject: Re: [gentoo-security] Kernel Security + KISS
Date: Mon, 18 Feb 2008 05:43:35 +0800	[thread overview]
Message-ID: <b18fbe3c0802171343t2c6999c2l3a7efe57f9fd589f@mail.gmail.com> (raw)
In-Reply-To: <200802171846.01731.jaervosz@gentoo.org>

What specific kernel knowledge is needed to get a Kernel advisory up
and running ?

   Ed

On Feb 18, 2008 1:46 AM, Sune Kloppenborg Jeppesen <jaervosz@gentoo.org> wrote:
> On Saturday 16 February 2008, Casey Link wrote:
> > I understand the logic behind not including kernel vulnerabilities in
> > regular GLSAs but in that thread
> > an up and coming solution (KISS) was mentioned. That was back in 2005
> > and now according to the Gentoo Kernel Security sub-project page the
> > project is stalled. Whatever happened to the KISS project?
> I sadly died before going live and the original kernel developer left.
>
> > I think notifying users of relevant kernel vulnerabilities is
> > important and I would like to help if possible. What is the current
> > state of things regarding kernel vulnerability reporting?
> I agree. However we need people with kernel knowledge and time to handle
> security issues for all kernel sources.
>
> Anyone interested should mail security@gentoo.org.
>
> --
> Sune Kloppenborg Jeppesen
> Gentoo Linux Security Team
>
> --
> gentoo-security@lists.gentoo.org mailing list
>
>
-- 
gentoo-security@lists.gentoo.org mailing list



  reply	other threads:[~2008-02-17 21:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 22:57 [gentoo-security] Kernel Security + KISS Casey Link
2008-02-17  0:42 ` Calum
2008-02-17 17:46 ` Sune Kloppenborg Jeppesen
2008-02-17 21:43   ` Eduardo Tongson [this message]
2008-02-18  4:12     ` Robert Buchholz
2008-02-20 18:59       ` Harlan Lieberman-Berg
2008-02-20 19:28         ` C. Bergström
2008-02-20 22:55         ` Ned Ludd
2008-02-21  3:16           ` Eduardo Tongson
2008-02-21  6:05             ` Casey Link
2008-02-21  6:20               ` Juan Pablo Olivera
2008-02-21  7:02                 ` Arthur Bispo de Castro
2008-02-21  9:14                   ` nick loeve
2008-02-21  9:34                     ` George Prowse
2008-02-21 13:09                       ` Robert Joslyn
2008-02-21 13:35                         ` Casey Link
2008-02-21 13:52                           ` Eduardo Tongson
2008-02-21 16:22                             ` George Prowse
2008-02-21 19:28                               ` doppelgaenger
2008-02-22  2:26                                 ` Eduardo Tongson
2008-02-22  3:55                                   ` Casey Link
2008-02-23  0:48                                     ` Marc Riemer
2008-02-24 13:43                                     ` Sune Kloppenborg Jeppesen
2008-02-21  9:30                   ` Marcin Dylewski
2008-02-21  9:54             ` Peter Hjalmarsson
2008-02-21 12:35               ` Eduardo Tongson
2008-02-21 13:32                 ` Sune Kloppenborg Jeppesen
2008-02-25 18:10 ` Simon Zehntner

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=b18fbe3c0802171343t2c6999c2l3a7efe57f9fd589f@mail.gmail.com \
    --to=propolice@gmail.com \
    --cc=gentoo-security@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