public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Reffett <creffett@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Thu, 31 Jan 2019 19:41:52 -0500	[thread overview]
Message-ID: <c82828ce-9b23-1edf-89ca-84eeef5437c8@gentoo.org> (raw)
In-Reply-To: <1548943008.796.1.camel@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1671 bytes --]

On 1/31/2019 8:56 AM, Michał Górny wrote:
> 
> 3. Before signing a user identifier, make sure to:
> 
>    b. Verify the person's real name (at least for the user identifier
>       used for copyright purposes).  This is usually done through
>       verifying an identification document with photograph.  It is
>       a good idea to ask for the document type earlier, and read on
>       forgery protections used.
> 
>       In some cases, alternate methods of verifying the identity may be
>       used if they provide equivalent or better level of reliability.
>       This can include e.g. use of national online identification
>       systems or bank transfers.
> 

I concur with the other comments people have made about this being an
unnecessarily restrictive burden, but let me pose a more philosophical
question: _why should proving my real name matter_? It's irrelevant that
I can prove my real name is in fact Chris Reffett, what's more important
is that there is somebody claiming the identity "creffett" whom people
(theoretically) trust as a developer. If I can't prove that that's my
real name, does that actually make a difference as to my trustworthiness
as a dev? It's the online "persona," if you will, that people trust, and
I don't see how verifying my name changes that. Now if I were trying to
use my PGP key as proof of my real-world identity, sure, it's a
reasonable concern, but I expect that if I'm involved in something like
that I would have to supply a scan of an identity document anyway.

And since I know someone will bring it up: yes, that is in fact my real
name. I'm just making a point.

-creffett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 885 bytes --]

  parent reply	other threads:[~2019-02-01  0:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 13:56 [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust Michał Górny
2019-01-31 14:21 ` Brian Evans
2019-01-31 15:33   ` Matthew Thode
2019-02-01  2:48   ` Sam Jorna (wraeth)
2019-02-01  6:57   ` Michał Górny
2019-02-01 14:43     ` Brian Evans
2019-02-02  6:00     ` desultory
2019-01-31 15:32 ` Matthew Thode
2019-02-01 12:47   ` Andreas K. Huettel
2019-02-01 14:17     ` Cynede
2019-02-01 14:32       ` Rich Freeman
2019-02-01 14:53         ` Kristian Fiskerstrand
2019-02-01 17:27           ` Kristian Fiskerstrand
2019-02-01 20:46             ` Rich Freeman
2019-02-02  6:02     ` desultory
2019-02-01 14:20   ` Michał Górny
2019-01-31 16:33 ` Kristian Fiskerstrand
2019-01-31 16:35 ` Alec Warner
2019-01-31 20:29   ` Kristian Fiskerstrand
2019-01-31 21:40     ` Alec Warner
2019-01-31 22:00       ` Kristian Fiskerstrand
2019-01-31 22:49       ` Michael Orlitzky
2019-02-01  0:09         ` Rich Freeman
2019-02-01  0:47           ` Kristian Fiskerstrand
2019-01-31 17:33 ` Rich Freeman
2019-02-01 12:51   ` Andreas K. Huettel
2019-02-01 13:25   ` Michał Górny
2019-02-02  5:55     ` desultory
2019-02-02 13:47       ` Rich Freeman
2019-01-31 19:25 ` Kristian Fiskerstrand
2019-02-01  0:41 ` Chris Reffett [this message]
2019-02-01  0:42   ` Kristian Fiskerstrand
2019-02-01  0:55     ` Chris Reffett
2019-02-01  1:56       ` Rich Freeman
2019-02-01 12:52         ` Andreas K. Huettel
2019-02-02  5:54 ` desultory

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=c82828ce-9b23-1edf-89ca-84eeef5437c8@gentoo.org \
    --to=creffett@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox