projects / linux-2.6-microblaze.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9fe64e1) | patch
docs: Clarify details for reporting security bugs
authorKees Cook <keescook@chromium.org>
Mon, 6 Mar 2017 19:13:51 +0000 (11:13 -0800)
committerJonathan Corbet <corbet@lwn.net>
Tue, 7 Mar 2017 07:26:03 +0000 (00:26 -0700)
commit49978be705dd7c202f58bb401ce82bdca6cf9756
tree1a822cdc36309090fde8df7e1a5d01417b02f752tree
parent9fe64e15148d1ff81fa0bcb5fd58531e3ae2aa3acommit | diff
docs: Clarify details for reporting security bugs

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>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/admin-guide/security-bugs.rst diff | blob | history
MicroBlaze GIT Repository