From: Matthew Thode <prometheanfire@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Thu, 31 Jan 2019 09:32:28 -0600 [thread overview]
Message-ID: <20190131153228.w2jb4txsm6d3iabh@gentoo.org> (raw)
In-Reply-To: <1548943008.796.1.camel@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]
On 19-01-31 14:56:48, Michał Górny wrote:
> Motivation
> ==========
>
> While Gentoo observes the status of OpenPGP web of trust for many years,
> there never has been a proper push to get all developers covered by it
> or even formalize the rules of signing one another's keys. Apparently,
> there are still many Gentoo developers who do not have their
> ``@gentoo.org`` UID signed by another active developer. Historically
> there were also cases of developers signing others' UIDs without
> actually verifying their identity. [#WOT-GRAPH]_ [#WOT-STATS]_
>
> The web of trust is usually considered secondary to Gentoo's internal
> trust system based on key fingerprints stored in LDAP and distributing
> via the website. While this system reliably covers all Gentoo
> developers, it has three major drawbacks:
>
> 1. It is entirely customary and therefore requires customized software
> to use. In other words, it's of limited usefulness to people outside
> Gentoo or does not work out of the box there.
s/customary/custom?
>
> 2. At least in the current form, it is entirely limited to Gentoo
> developers. As such, it does not facilitate trust between them
> and the outer world.
>
> 3. It relies on a centralized server whose authenticity is in turn
> proved via PKI. This model is generally considered weak.
>
> Even if this trust system is to stay being central to Gentoo's needs,
> it should be beneficial for Gentoo developers start to improving
> the OpenPGP web of trust, both for the purpose of improving Gentoo's
> position in it and for the purpose of enabling better trust coverage
> between Gentoo developers, users and other people.
>
> Furthermore, the recent copyright policy established in GLEP 76
> introduces the necessity of verifying real names of developers. Given
> that the Foundation wishes to avoid requesting document scans or other
> form of direct verification, the identity verification required
> for UID signing can also serve the needs of verifying the name
> for Certificate of Origin sign-off purposes. [#GLEP76]_
>
I don't see anything in glep 76 about requiring verification of the
signatures. It's my view (as trustee) that assertation by the signer
that 'this is my signature' is sufficient. Introducing more
verification should not be needed. That said I do think switching to a
WoT model has some merit, it's just that the name verification is a
side benefit, not a primary reason for the switch.
> Backwards Compatibility
> =======================
>
> Gentoo does not use any particular web of trust policy at the moment.
> Not all of existing signatures conform to the new policy. Therefore,
> approving it is going to require, in some cases:
>
> a. replacing non-conformant user identifiers,
>
> b. revoking non-conformant signatures.
>
> Naturally, those actions can only be carried off by cooperating key
> owners.
>
> The policy specifies transitional periods for developers whose keys are
> not signed by anyone in the community yet.
>
I do wonder about how this part will be enforced.
--
Matthew Thode
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-01-31 15:32 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 [this message]
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
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=20190131153228.w2jb4txsm6d3iabh@gentoo.org \
--to=prometheanfire@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