Messages in this thread | | | From | Kees Cook <> | Date | Mon, 6 Mar 2017 23:47:26 -0800 | Subject | Re: [PATCH] docs: Clarify details for reporting security bugs |
| |
On Mon, Mar 6, 2017 at 11:27 PM, Jonathan Corbet <corbet@lwn.net> wrote: > 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.
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?
Ah, maybe I was looking at the wrong thing. Regardless, it seems like security-bugs.rst is the same "type" as "submitting-patches.rst", so perhaps it should move?
-Kees
-- Kees Cook Pixel Security
| |