linux-kernel - Re: [PATCH] docs: Clarify details for reporting security bugs

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: <20170307002740.6eda92fa@lwn.net>
Date:   Tue, 7 Mar 2017 00:27:40 -0700
From:   Jonathan Corbet <corbet@....net>
To:     Kees Cook <keescook@...omium.org>
Cc:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        security@...nel.org
Subject: Re: [PATCH] docs: Clarify details for reporting security bugs

On Mon, 6 Mar 2017 11:13:51 -0800
Kees Cook <keescook@...omium.org> wrote:

> The kernel security team is regularly asked to provide CVE identifiers,
> which we don't normally do. This updates the documentation to mention
> this and adds some more details about coordination and patch handling
> that come up regularly. Based on an earlier draft by Willy Tarreau.
> 
> Signed-off-by: Kees Cook <keescook@...omium.org>
> Acked-by: Willy Tarreau <w@....eu>

Seems good, applied to the docs tree, thanks.

> Related question: shouldn't security-bugs.rst and submitting-patches.rst live
> in /process/ rather than /admin-guide/ ?

The former should maybe be there, depending on just who we think it
should be aimed at, I guess.  submitting-patches.rst is already in
process/, though, so I'm not quite sure I understand that question?

Thanks,

jon