Re: [openpgp] Fingerprint requirements for OpenPGP

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Tue, 12 April 2016 17:02 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B761D12E47F for <openpgp@ietfa.amsl.com>; Tue, 12 Apr 2016 10:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id deEEnfkkIG2H for <openpgp@ietfa.amsl.com>; Tue, 12 Apr 2016 10:02:33 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by ietfa.amsl.com (Postfix) with ESMTP id B472F12E372 for <openpgp@ietf.org>; Tue, 12 Apr 2016 10:02:26 -0700 (PDT)
Received: from fifthhorseman.net (unknown [38.109.115.130]) by che.mayfirst.org (Postfix) with ESMTPSA id C2A98F991; Tue, 12 Apr 2016 13:02:25 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id A9CF8200B0; Tue, 12 Apr 2016 13:02:25 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Salz, Rich" <rsalz@akamai.com>, Derek Atkins <derek@ihtfp.com>
In-Reply-To: <501e915a203a436193f15331cf99d1c7@usma1ex-dag1mb1.msg.corp.akamai.com>
References: <87vb3nslqh.fsf@alice.fifthhorseman.net> <sjmbn5e3na2.fsf@securerf.ihtfp.org> <87twj6pzz5.fsf@alice.fifthhorseman.net> <daf936848f9c4308d9b5fd33f4b3a3cf.squirrel@mail2.ihtfp.org> <877fg2bwq5.fsf@alice.fifthhorseman.net> <501e915a203a436193f15331cf99d1c7@usma1ex-dag1mb1.msg.corp.akamai.com>
User-Agent: Notmuch/0.21+128~g620f892 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Tue, 12 Apr 2016 13:02:25 -0400
Message-ID: <87y48iahge.fsf@alice.fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/TCSfnCmP294lsza0Oc59wS-wD8s>
Cc: IETF OpenPGP <openpgp@ietf.org>
Subject: Re: [openpgp] Fingerprint requirements for OpenPGP
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Apr 2016 17:02:34 -0000

On Tue 2016-04-12 12:52:49 -0400, "Salz, Rich" <rsalz@akamai.com> wrote:
>> One concern i have with existing keyserver infrastructure is that anyone can
>> upload a key with any e-mail address.  This could result in a lookup that
>> returns dozens or hundreds of keys.
>
> It would be nice if PGP were so successful :)

I agree with you, but this concern isn't about success, it's about a
malicious flooding attack :/

> The keyservers can address this by sending PGP-encrypted "please confirm" email.

that doesn't work with the model of the keyserver network, where
untrusted peer keyservers gossip data between each other.  i'm pretty
sure we don't want a "please confirm" e-mail from each keyserver
operator, and i think most keyserver operators don't want the
responsibility of running such a vetting service.

If the answer is "throw away the keyserver network" then that's one
thing; but if we think there needs to be a public directory lookup, then
we need a clear explanation of how that works.  i understand from
Vincent's recent thread that people seem to be actively thinking about
alternatives, which is a Good Thing.  but even Vincent's thread doesn't
seem to cover revocation.

               --dkg