lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <202508141423.55DECF0601@keescook>
Date: Thu, 14 Aug 2025 14:23:07 -0700
From: Kees Cook <kees@...nel.org>
To: Willy Tarreau <w@....eu>
Cc: Jonathan Corbet <corbet@....net>, security@...nel.org,
	workflows@...r.kernel.org, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 2/2] Documentation: smooth the text flow in the security
 bug reporting process

On Thu, Aug 14, 2025 at 09:27:30PM +0200, Willy Tarreau wrote:
> The text was presenting the team, the the e-mail address, then some of
> the expectations, then what form of e-mail is expected. By switching
> the e-mail paragraph two paragraphs later and dropping the "Contact"
> sub-section, we can have a more natural flow that presents the team,
> then its expectation, then how to best contribute, then where to send.
> 
> And more importantly, it increases the chances that reporters have read
> the prerequisites before finding the e-mail address.
> 
> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
> Signed-off-by: Willy Tarreau <w@....eu>

Reviewed-by: Kees Cook <kees@...nel.org>

-- 
Kees Cook

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ