linux-kernel - Re: [PATCH 4/4] Documentation/process: add transparency promise to list subscription

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.1909161028340.10731@nanos.tec.linutronix.de>
Date:   Mon, 16 Sep 2019 10:30:02 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Greg KH <gregkh@...uxfoundation.org>
cc:     Dave Hansen <dave.hansen@...ux.intel.com>,
        linux-kernel@...r.kernel.org, corbet@....net, sashal@...nel.org,
        ben@...adent.org.uk, labbott@...hat.com, andrew.cooper3@...rix.com,
        tsoni@...eaurora.org, keescook@...omium.org, tony.luck@...el.com,
        linux-doc@...r.kernel.org, dan.j.williams@...el.com
Subject: Re: [PATCH 4/4] Documentation/process: add transparency promise to
 list subscription

On Wed, 11 Sep 2019, Greg KH wrote:
> On Tue, Sep 10, 2019 at 10:26:52AM -0700, Dave Hansen wrote:
> > 
> > From: Dave Hansen <dave.hansen@...ux.intel.com>
> > 
> > Transparency is good.  It it essential for everyone working under an
> > embargo to know who is involved and who else is a "knower".  Being
> > transparent allows everyone to always make informed decisions about
> > ongoing participating in a mitigation effort.
> > 
> > Add a step to the subscription process which will notify existing
> > subscribers when a new one is added.
> 
> As I don't run the mailing list software here, I don't know how much of
> a burden adding this support to it would be, so I'll defer to Thomas.
> 
> We could just have something like "All new people need to announce
> themselves" rule like many other private mailing lists have at times.
> That would put the burden on the new person once, instead of the list
> manager for every time a new person is added.

That's trivial and can be fully automated into the list scripts. I'll put
that on to the todo list as I'm in the process of cleaning stuff up and
fixing the documentation before pushing the whole pile out.

Thanks,

	tglx