Add a name for the document and convert the sections to ReST markups. Signed-off-by: Mauro Carvalho Chehab <mche...@s-opensource.com> --- Documentation/kernel-development/SecurityBugs.rst | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/Documentation/kernel-development/SecurityBugs.rst b/Documentation/kernel-development/SecurityBugs.rst index a660d494c8ed..5f61bd4bc8ef 100644 --- a/Documentation/kernel-development/SecurityBugs.rst +++ b/Documentation/kernel-development/SecurityBugs.rst @@ -1,9 +1,13 @@ +Security bugs +============= + Linux kernel developers take security very seriously. As such, we'd like to know when a security bug is found so that it can be fixed and disclosed as quickly as possible. Please report security bugs to the Linux kernel security team. -1) Contact +Contact +------- The Linux kernel security team can be contacted by email at <secur...@kernel.org>. This is a private list of security officers @@ -17,7 +21,8 @@ REPORTING-BUGS if you are unclear about what information is helpful. Any exploit code is very helpful and will not be released without consent from the reporter unless it has already been made public. -2) Disclosure +Disclosure +---------- The goal of the Linux kernel security team is to work with the bug submitter to bug resolution as well as disclosure. We prefer @@ -32,7 +37,8 @@ disclosure is from immediate (esp. if it's already publicly known) to a few weeks. As a basic default policy, we expect report date to disclosure date to be on the order of 7 days. -3) Non-disclosure agreements +Non-disclosure agreements +------------------------- The Linux kernel security team is not a formal body and therefore unable to enter any non-disclosure agreements. -- 2.7.4 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
