From: Willy Tarreau <w@1wt.eu>
To: Rafa dv <rdv.post@googlemail.com>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: Linux Kernel Bug - Who to talk to?
Date: Sun, 13 Sep 2009 13:33:06 +0200 [thread overview]
Message-ID: <20090913113305.GA27185@1wt.eu> (raw)
In-Reply-To: <395a49390909130403o334c5347qd114e0d75dce8a56@mail.gmail.com>
On Sun, Sep 13, 2009 at 12:03:59PM +0100, Rafa dv wrote:
> Hello all,
>
> Just a quick question. Who should I contact in regards to a Linux
> kernel security bug?
Either you think it's not particularly serious and you can talk about it
here, or you prefer to restrict discussion about it in a small committee
before it gets fixed, and you can mail security@kernel.org for that
purpose.
If there's a known maintainer for the subsystem affected by this bug, it
may help to CC him too.
Regards,
Willy
prev parent reply other threads:[~2009-09-13 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-13 11:03 Rafa dv
2009-09-13 11:33 ` Willy Tarreau [this message]
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=20090913113305.GA27185@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=rdv.post@googlemail.com \
/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®