linux-kernel - Re: [PATCH] [v2] docs: clarify security-bugs disclosure policy

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: <20180309204526.56301f43@alans-desktop>
Date:   Fri, 9 Mar 2018 20:45:26 +0000
From:   Alan Cox <gnomes@...rguk.ukuu.org.uk>
To:     Dave Hansen <dave.hansen@...ux.intel.com>
Cc:     linux-kernel@...r.kernel.org, dan.j.williams@...el.com,
        tglx@...utronix.de, gregkh@...uxfoundation.org,
        torvalds@...ux-foundation.org, aarcange@...hat.com,
        luto@...nel.org, keescook@...gle.com, tim.c.chen@...ux.intel.com,
        viro@...iv.linux.org.uk, akpm@...ux-foundation.org,
        linux-doc@...r.kernel.org, corbet@....net, mark.rutland@....com
Subject: Re: [PATCH] [v2] docs: clarify security-bugs disclosure policy

On Wed, 07 Mar 2018 13:46:24 -0800
Dave Hansen <dave.hansen@...ux.intel.com> wrote:

> From: Dave Hansen <dave.hansen@...ux.intel.com>
> 
> I think we need to soften the language a bit.  It might scare folks
> off, especially the:
> 
> 	 We prefer to fully disclose the bug as soon as possible.
> 
> which is not really the case.  Linus says:
> 
> 	It's not full disclosure, it's not coordinated disclosure,
> 	and it's not "no disclosure".  It's more like just "timely
> 	open fixes".
> 
> I changed a bit of the wording in here, but mostly to remove the word
> "disclosure" since it seems to mean very specific things to people
> that we do not mean here.
> 

If you want to be taken seriously then I think minimum you also need to
- Give a GPG key for messages to the list
- State what security is in place (encryption etc) to protect the list
  itself

There are probably a lot more things people would ask but given the
policy now clear that it's basically just an 'early tip off'/'make sure
Linus doesn't miss this' list for very short notification periods doesn't
matter so much.

Alan