diff options
| author | Willy Tarreau <w@1wt.eu> | 2025-11-29 17:17:41 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2025-12-23 01:32:03 +0300 |
| commit | ceddb2c001d9f22fd3712dc0425c3a15bc504461 (patch) | |
| tree | 00f4dd713081c89a8f16cf0f93489cf818bb3794 | |
| parent | 273aa250f138c996f351be4a2556043ec8bbc9a5 (diff) | |
| download | linux-ceddb2c001d9f22fd3712dc0425c3a15bc504461.tar.xz | |
Documentation: insist on the plain-text requirement for security reports
As the trend of AI-generated reports is growing, the trend of unreadable
reports in gimmicky formats is following, and we cannot request that
developers rely on online viewers to be able to read a security report
full for formatting tags. Let's just insist on the plain text requirement
a bit more.
Signed-off-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Message-ID: <20251129141741.19046-1-w@1wt.eu>
| -rw-r--r-- | Documentation/process/security-bugs.rst | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/Documentation/process/security-bugs.rst b/Documentation/process/security-bugs.rst index 84657e7d2e5b..c0cf93e11565 100644 --- a/Documentation/process/security-bugs.rst +++ b/Documentation/process/security-bugs.rst @@ -33,12 +33,16 @@ that can speed up the process considerably. It is possible that the security team will bring in extra help from area maintainers to understand and fix the security vulnerability. -Please send plain text emails without attachments where possible. +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. +Markdown, HTML and RST formatted reports are particularly frowned upon since +they're quite hard to read for humans and encourage to use dedicated viewers, +sometimes online, which by definition is not acceptable for a confidential +security report. Disclosure and embargoed information ------------------------------------ |