linux-kernel - Re: Code of Conduct: Let's revamp it.

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: <d364f33b-fbb4-57e0-78f5-302cd5c9050f@petrovitsch.priv.at>
Date:   Sat, 22 Sep 2018 01:59:55 +0200
From:   Bernd Petrovitsch <bernd@...rovitsch.priv.at>
To:     "jonsmirl@...il.com" <jonsmirl@...il.com>,
        Theodore Tso <tytso@....edu>, fche@...hat.com,
        riel@...riel.com, ec429@...tab.net,
        Olof Johansson <olof@...om.net>,
        Jonathan Corbet <corbet@....net>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: Code of Conduct: Let's revamp it.

On 22/09/2018 01:31, jonsmirl@...il.com wrote:
[...]
> How does this part apply to email addresses used to commit code?
> 
> * Publishing others’ private information, such as a physical or electronic
> address, without explicit permission

I need an (explicit) permission to "publish" an already published email
address which is already world-wide known because it can be found by the
simplest and worst search engine as the email address is in public
mailing list archives and git repos?

Sounds pretty absurd as the people themselves already published their
email address.

IMHO you cannot "publish" already published stuff.

MfG,
	Bernd, NAL
-- 
Bernd Petrovitsch                  Email : bernd@...rovitsch.priv.at
                     LUGA : http://www.luga.at

Download attachment "pEpkey.asc" of type "application/pgp-keys" (1779 bytes)