From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project <gentoo-project@lists.gentoo.org>
Subject: Re: [gentoo-project] pre-GLEP: Gentoo OpenPGP web of trust
Date: Thu, 31 Jan 2019 19:09:11 -0500 [thread overview]
Message-ID: <CAGfcS_mDRRQsA6X=atPFGv9mh+i=5-DOn7qPpXDoevummsicwQ@mail.gmail.com> (raw)
In-Reply-To: <fb2d6148-3948-68ba-3673-8301b4e97857@gentoo.org>
On Thu, Jan 31, 2019 at 5:49 PM Michael Orlitzky <mjo@gentoo.org> wrote:
>
> On 1/31/19 4:40 PM, Alec Warner wrote:
> >
> > So we have a website that lists all of our developers and their gpg-fps
> > already. I realize that mgorny will object that this is a 'nonstandard
> > tool' or somesuch, but I think from my POV its a pretty straightforward
> > tool. Obviously it requires trusting www.gentoo.org
> > <http://www.gentoo.org> and our CA (of which we do not run our own, so
> > it is letsencrypt, IIRC.)
> >
>
> The problem with the PKI is that even if LetsEncrypt is trustworthy,
> everyone else that you trust is not. If you're in whatever theocracy is
> in vogue for murdering its citizens this week, then you want to be sure
> that your government can't forge a certificate for www.gentoo.org (which
> says the "f" word a lot) on-the-fly. Of course, they all can. The list
> of trusted CAs in modern browsers is basically a "who's who" of the
> least trustworthy people on Earth.
These same governments print up the IDs the GLEP proposes that
developers verify.
Also, while governments like the US/EU might put a ton of security
features in those IDs, I suspect that quite a few governments issue
IDs with about as many anti-tamper features as a library card. With a
WoT the chain is as strong as its weakest link.
> With the web of trust, I am at least trusting someone who is trusting
> someone who is trusting someone who is trusting someone that I've met in
> person.
You use the word "trust," but keep in mind the only thing that last
person is verifying is that:
1. The person has an ID with a matching ID (issued by that theocracy
that murders its citizens).
2. The person has control over the email address somebody presented
to the recruiters. That would be the one that is reached via telecom
lines that go through the ISP controlled by that theocracy that
murders its citizens.
The person signing off on somebody's key won't be a close personal
friend of the applicant. They won't have been their mentor for the
last six months. They won't be on the same project, reviewing their
commits. They'll be a random developer who just happens to live
somewhat near the applicant. The actual mentors/etc would have been
in communication solely by email/IRC and will live on the other side
of the planet and probably will never actually meet the applicant in
person.
Now, perhaps the actual mentor will verify IDs/etc via webcam or
something like that, but you're still subject to the vulnerability of
the local government all the same, and if the mentor doesn't normally
interact via webcam they really won't know if the person on the other
end of the line is the person they've been interacting with all along.
If the threat model is state actors seeking to infiltrate Gentoo, then
the proposed methods are inadequate. If the threat model is something
more likely such as misc vandals/etc, then we can probably relax
things further.
--
Rich
next prev parent reply other threads:[~2019-02-01 0:09 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 [this message]
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='CAGfcS_mDRRQsA6X=atPFGv9mh+i=5-DOn7qPpXDoevummsicwQ@mail.gmail.com' \
--to=rich0@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