Documentation/security-bugs: Explain why plain text is preferred
PATCH 1/1 Documentation/security-bugs: Explain why plain text is preferred
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
--- Documentation/admin-guide/security-bugs.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
Documentation/admin-guide/security-bugs.rst +8 -1
@@ -21,11 +21,18 @@ understand and fix the security vulnerability. As it is with any bug, the more information provided the easier it will be to diagnose and fix. Please review the procedure outlined in -admin-guide/reporting-bugs.rst if you are unclear about what +:doc:`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. +Please send plain text emails without attachments where possible. +It is much harder to have a context-quoted discussion about a complex +issue if all the details are hidden away in attachments. Think of it like a +:doc:`regular patch submission <../process/submitting-patches>` +(even if you don't have a patch yet): describe the problem and impact, list +reproduction steps, and follow it with a proposed fix, all in plain text. + Disclosure and embargoed information ------------------------------------
Signature · 5 lines
2.25.1 -- Kees Cook
Quoted 20 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>--- Documentation/admin-guide/security-bugs.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)Documentation/admin-guide/security-bugs.rst +1
-1@@ -21,11 +21,18 @@ understand and fix the security vulnerability. As it is with any bug, the more information provided the easier it will be to diagnose and fix. Please review the procedure outlined in -admin-guide/reporting-bugs.rst if you are unclear about what +:doc:`reporting-bugs` if you are unclear about what information is helpful. Any exploit code is very helpful and will not
Documentation/admin-guide/security-bugs.rst understand and fix the security vulnerability. · line 35
Quoted 10 lines
Documentation/admin-guide/security-bugs.rst +7
-0be released without consent from the reporter unless it has already been made public. +Please send plain text emails without attachments where possible. +It is much harder to have a context-quoted discussion about a complex +issue if all the details are hidden away in attachments. Think of it like a +:doc:`regular patch submission <../process/submitting-patches>` +(even if you don't have a patch yet): describe the problem and impact, list +reproduction steps, and follow it with a proposed fix, all in plain text. +
Hopefully "plain text" implies unencrypted as much as it does "not html".
Will
Quoted 24 lines · Will Deacon
Quoted 23 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>--- Documentation/admin-guide/security-bugs.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)Documentation/admin-guide/security-bugs.rst +1
-1@@ -21,11 +21,18 @@ understand and fix the security vulnerability. As it is with any bug, the more information provided the easier it will be to diagnose and fix. Please review the procedure outlined in -admin-guide/reporting-bugs.rst if you are unclear about what +:doc:`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.
Quoted 9 lines
Documentation/admin-guide/security-bugs.rst understand and fix the security vulnerability. · line 35
Quoted 7 lines
Documentation/admin-guide/security-bugs.rst +7
-0+Please send plain text emails without attachments where possible. +It is much harder to have a context-quoted discussion about a complex +issue if all the details are hidden away in attachments. Think of it like a +:doc:`regular patch submission <../process/submitting-patches>` +(even if you don't have a patch yet): describe the problem and impact, list +reproduction steps, and follow it with a proposed fix, all in plain text. +Acked-by Will Deacon <[email protected]>
Thanks!
Quoted 2 lines
Hopefully "plain text" implies unencrypted as much as it does "not html".
I decided not to write a paragraph about how security@ isn't a role-account with a separate GPG key etc etc. Those cases are rare enough that I don't think it (yet) warrants a paragraph here. I want to strike a balance between "all your questions are answered" and "there's too much here for me to find the answer to my question". :)
Signature · 1 line
Kees Cook
Willy Tarreau
Acked-byQuoted 3 lines · Will Deacon
Acked-by Will Deacon <[email protected]>Hopefully "plain text" implies unencrypted as much as it does "not html".
I would have liked "(i.e. not html)" to be added after "plain text", but I figured that those who do that often don't even know what this means so that will probably not help them avoid their messages being stored into a spambox :-/
Willy
Quoted 34 lines · Will Deacon
Quoted 20 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>--- Documentation/admin-guide/security-bugs.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)Documentation/admin-guide/security-bugs.rst +1
-1@@ -21,11 +21,18 @@ understand and fix the security vulnerability. As it is with any bug, the more information provided the easier it will be to diagnose and fix. Please review the procedure outlined in -admin-guide/reporting-bugs.rst if you are unclear about what +:doc:`reporting-bugs` if you are unclear about what information is helpful. Any exploit code is very helpful and will notDocumentation/admin-guide/security-bugs.rst understand and fix the security vulnerability. · line 35
Quoted 10 lines
Documentation/admin-guide/security-bugs.rst +7
-0be released without consent from the reporter unless it has already been made public. +Please send plain text emails without attachments where possible. +It is much harder to have a context-quoted discussion about a complex +issue if all the details are hidden away in attachments. Think of it like a +:doc:`regular patch submission <../process/submitting-patches>` +(even if you don't have a patch yet): describe the problem and impact, list +reproduction steps, and follow it with a proposed fix, all in plain text. +Acked-by Will Deacon <[email protected]>
Quoted 1 line
Hopefully "plain text" implies unencrypted as much as it does "not html".
Or that RST crap :-(
Quoted 5 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>
Thanks,
Signature · 2 lines
Jiri Kosina SUSE Labs
Quoted 5 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>
Thanks
--
Gustavo
Quoted 5 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>
Thanks for this, that will hopefully keep us from having to say the same thing over and over :)
Peter Zijlstra
NAKQuoted 14 lines · Kees Cook
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>--- Documentation/admin-guide/security-bugs.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)Documentation/admin-guide/security-bugs.rst +0
-0
Documentation/admin-guide/security-bugs.rst understand and fix the security vulnerability. · line 24
Quoted 5 lines
Documentation/admin-guide/security-bugs.rst +1
-1@@ -21,11 +21,18 @@ understand and fix the security vulnerability. As it is with any bug, the more information provided the easier it will be to diagnose and fix. Please review the procedure outlined in -admin-guide/reporting-bugs.rst if you are unclear about what +:doc:`reporting-bugs` if you are unclear about what
I can do 'gf' on Documentation/admin-guide/reporting-bugs.rst, I can do didly squat with crap like :doc:'reporting-bugs'.
NAK
Documentation/admin-guide/security-bugs.rst understand and fix the security vulnerability. · line 32
Quoted 8 lines
Documentation/admin-guide/security-bugs.rst +4
-0information 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. +Please send plain text emails without attachments where possible. +It is much harder to have a context-quoted discussion about a complex +issue if all the details are hidden away in attachments. Think of it like a +:doc:`regular patch submission <../process/submitting-patches>`
More unusable references.
Documentation/admin-guide/security-bugs.rst understand and fix the security vulnerability. · line 35
Quoted 3 lines
Documentation/admin-guide/security-bugs.rst +3
-0+(even if you don't have a patch yet): describe the problem and impact, list +reproduction steps, and follow it with a proposed fix, all in plain text. +
You forgot to mention that opening complex file formats is a security risk all of its own.
Quoted 8 lines · On Thu, 9 Jul 2020 11:11:30 -0700 Kees Cook <[email protected]> wrote:
The security contact list gets regular reports contained in archive attachments. This tends to add some back-and-forth delay in dealing with security reports since we have to ask for plain text, etc.
Signed-off-by Kees Cook <[email protected]>--- Documentation/admin-guide/security-bugs.rst | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
Applied, thanks.
jon