From: Jonathan Corbet <corbet@lwn.net>
To: Kees Cook <keescook@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
security@kernel.org
Subject: Re: [PATCH] docs: Clarify details for reporting security bugs
Date: Tue, 7 Mar 2017 00:27:40 -0700 [thread overview]
Message-ID: <20170307002740.6eda92fa@lwn.net> (raw)
In-Reply-To: <20170306191351.GA87394@beast>
On Mon, 6 Mar 2017 11:13:51 -0800
Kees Cook <keescook@chromium.org> wrote:
> The kernel security team is regularly asked to provide CVE identifiers,
> which we don't normally do. This updates the documentation to mention
> this and adds some more details about coordination and patch handling
> that come up regularly. Based on an earlier draft by Willy Tarreau.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> Acked-by: Willy Tarreau <w@1wt.eu>
Seems good, applied to the docs tree, thanks.
> Related question: shouldn't security-bugs.rst and submitting-patches.rst live
> in /process/ rather than /admin-guide/ ?
The former should maybe be there, depending on just who we think it
should be aimed at, I guess. submitting-patches.rst is already in
process/, though, so I'm not quite sure I understand that question?
Thanks,
jon
next prev parent reply other threads:[~2017-03-07 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 19:13 [PATCH] docs: Clarify details for reporting security bugs Kees Cook
2017-03-07 7:27 ` Jonathan Corbet [this message]
2017-03-07 7:47 ` Kees Cook
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=20170307002740.6eda92fa@lwn.net \
--to=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=security@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.