LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Joe Perches <joe@perches.com>, linux-kernel@vger.kernel.org
Subject: Re: PSA: Do not use "Reported-By" without reporter's approval
Date: Fri, 24 May 2019 00:57:08 -0400	[thread overview]
Message-ID: <20190524045708.GH2532@mit.edu> (raw)
In-Reply-To: <20190522195804.GC21412@chatter.i7.local>

On Wed, May 22, 2019 at 03:58:04PM -0400, Konstantin Ryabitsev wrote:
> > If the report is public, and lists like vger are public,
> > then using a Reported-by: and/or a Link: are simply useful
> > history and tracking information.
> 
> I'm perfectly fine with Link:, however Reported-By: usually has the person's
> name and email address (i.e. PII data per GDPR definition). If that pehrson
> submitted the bug report via bugzilla.kernel.org or a similar resource,
> their expectation is that they can delete their account should they choose
> to to do so. However, if the patch containing Reported-By is committed to
> git, their PII becomes permanently and immutably recorded for any reasonable
> meaning of the word "forever."

Many (most?) bugzilla.kernel.org components result in e-mail getting
sent to vger.kernel.org mailing lists.  So even if they delete the
bugzilla account, there e-mail will be immortalized in lore.kernel.org
and their associated git repositories.

So perhaps a better approach is to put a warning alerting bug
reporters that submitting a bug means their e-mail will end up get
broadcasting in public mailing list archives and public git
repositories?

I assume distro engineers who are fixing bugs from their Distro
bugzillas which support non-public bugs already know that they
shouldn't be revealing their customers' identities.  But
realistically, while I agree it would be nice to ask people if they
don't mind being immortalized in git repositories, we should probably
warn people that when they submit a bug, or for that matter, send
e-mail to a kernel mailing list, they're going to be immortalized in a
git repository *already*.

						- Ted

  parent reply	other threads:[~2019-05-24  4:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-22 19:30 Konstantin Ryabitsev
2019-05-22 19:45 ` Joe Perches
2019-05-22 19:58   ` Konstantin Ryabitsev
2019-05-22 20:00     ` Joe Perches
2019-05-24  4:57     ` Theodore Ts'o [this message]
2019-05-24 12:54       ` Konstantin Ryabitsev
2019-05-24 15:06         ` Joe Perches
2019-05-23  5:53 ` Bhaskar Chowdhury

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190524045708.GH2532@mit.edu \
    --to=tytso@mit.edu \
    --cc=joe@perches.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: PSA: Do not use "Reported-By" without reporter'\''s approval' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).