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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 6, 2017 at 11:27 PM, Jonathan Corbet <corbet@xxxxxxx> wrote:
> On Mon, 6 Mar 2017 11:13:51 -0800
> Kees Cook <keescook@xxxxxxxxxxxx> 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@xxxxxxxxxxxx>
>> Acked-by: Willy Tarreau <w@xxxxxx>
>
> Seems good, applied to the docs tree, thanks.

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?

Ah, maybe I was looking at the wrong thing. Regardless, it seems like
security-bugs.rst is the same "type" as "submitting-patches.rst", so
perhaps it should move?

-Kees

-- 
Kees Cook
Pixel Security
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux