Documentation/security-bugs: Clarify treatment of embargoed information
authorWill Deacon <will.deacon@arm.com>
Mon, 22 Oct 2018 15:39:01 +0000 (16:39 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Tue, 23 Oct 2018 13:15:58 +0000 (14:15 +0100)
commit14fdc2c5318ae420e68496975f48dc1dbef52649
tree9fc359b5e6efa9ed6bf69125049aa32fa893d174
parent93048c0944150b316a15f92c41a4d626c8df37fd
Documentation/security-bugs: Clarify treatment of embargoed information

The Linux kernel security team has been accused of rejecting the idea of
security embargoes. This is incorrect, and could dissuade people from
reporting security issues to us under the false assumption that the
issue would leak prematurely.

Clarify the handling of embargoed information in our process
documentation.

Co-developed-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Kees Cook <keescook@chromium.org>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Acked-by: Laura Abbott <labbott@redhat.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Documentation/admin-guide/security-bugs.rst