linux-kernel - Re: [RFC PATCH v1 21/26] docs: reporting-bugs: details on writing and sending the report

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b1c84287-867b-5884-8cb5-f9f433014622@leemhuis.info>
Date:   Fri, 9 Oct 2020 09:38:14 +0200
From:   Thorsten Leemhuis <linux@...mhuis.info>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Jonathan Corbet <corbet@....net>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v1 21/26] docs: reporting-bugs: details on writing and
 sending the report

Many thx for you comments. Consider all the obvious spelling and


grammatical mistakes you pointed out fixed, I won't mention all of them


in this reply to keep things easier to follow.

Am 09.10.20 um 04:45 schrieb Randy Dunlap:
> On 10/1/20 1:39 AM, Thorsten Leemhuis wrote:

>> +   In both cases make sure to inform those that the MAINTAINERS file lists in
>> +   the section 'security contact'. Ideally CCing them on the mail with the
>> +   report. If you filed it in a bug tracker forward the reports text, but on top
> 
> parse error in first 2 sentences above...

Now reads:

In both cases make sure to mail your report to the addresses the 
MAINTAINERS file lists in the section 'security contact'. Ideally 
directly CC them when sending the report by mail.

Ciao, Thorsten