linux-kernel - Re: [PATCH v2 2/2] docs: clarify rules wrt tagging other people

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: <6d5f8ebb-790b-4b25-8cfd-3b016eb27dca@leemhuis.info>
Date: Sat, 16 Nov 2024 12:51:20 +0100
From: Thorsten Leemhuis <linux@...mhuis.info>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
 linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
 Laurent Pinchart <laurent.pinchart@...asonboard.com>,
 Simona Vetter <simona.vetter@...ll.ch>,
 Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Subject: Re: [PATCH v2 2/2] docs: clarify rules wrt tagging other people

On 16.11.24 12:38, Geert Uytterhoeven wrote:
> On Sat, Nov 16, 2024 at 10:39 AM Thorsten Leemhuis <linux@...mhuis.info> wrote:
>> The latter is not a theoretical issue, as one maintainer mentioned that
>> his employer received a EU GDPR (general data protection regulation)
>> complaint after exposing a email address used in bugzilla through a tag
>> in a patch description.
> 
> And once it's upstream there is not much we can do about that anymore,
> right?

Well, right. :-D I thought that was obvious, so I did not mentioned it
in the patch description. I considered mentioning it in the added text,
but in the end decided against it, as once an email address is exposed
in a patch posting it's kind of too late anyway, as it then ended up in
external archives we have no control over.

Ciao, Thorsten