From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Darren Hart <dvhart@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
netdev@vger.kernel.org
Subject: Re: [RFC] Any value in having a netdev FAQ?
Date: Thu, 18 Jul 2013 04:32:19 +0200 [thread overview]
Message-ID: <20130718023219.GR6401@order.stressinduktion.org> (raw)
In-Reply-To: <20130716025954.GC26761@windriver.com>
Thanks for the great FAQ!
On Mon, Jul 15, 2013 at 10:59:54PM -0400, Paul Gortmaker wrote:
> Q: I found a bug that might have possible security implications or similar.
> Should I mail the main netdev maintainer off-list?
>
> A: No. The current netdev maintainer has consistently requested that people
> use the mailing lists and not reach out directly. If you aren't OK with
> that, then perhaps consider using "security@kernel.org" instead.
I don't have a strong opinion on that, just a proposal (and I certainly don't
want to start another discussion about that):
Maybe we could give a hint about the linux-distros mailing list here, too?
<http://oss-security.openwall.org/wiki/mailing-lists/distros>
Thanks,
Hannes
prev parent reply other threads:[~2013-07-18 2:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 2:59 [RFC] Any value in having a netdev FAQ? Paul Gortmaker
2013-07-16 20:05 ` David Miller
2013-07-16 20:34 ` Darren Hart
2013-07-16 20:35 ` Darren Hart
2013-07-17 15:08 ` Paul Gortmaker
2013-07-16 20:32 ` Darren Hart
2013-07-17 15:18 ` Paul Gortmaker
2013-07-17 15:56 ` Joe Perches
2013-07-18 18:21 ` Benjamin Poirier
2013-07-16 20:42 ` Joe Perches
2013-07-18 1:55 ` Darren Hart
2013-07-18 13:33 ` Paul Gortmaker
2013-07-18 17:53 ` Rick Jones
2013-07-18 2:32 ` Hannes Frederic Sowa [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=20130718023219.GR6401@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=davem@davemloft.net \
--cc=dvhart@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=netdev@vger.kernel.org \
--cc=paul.gortmaker@windriver.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;
as well as URLs for NNTP newsgroup(s).