IETF Logo Mail Archive

Re: [openpgp] Modelling an abuse-resistant OpenPGP keyserver

ilf <ilf@zeromail.org> Tue, 16 April 2019 21:36 UTC

Return-Path: <ilf@zeromail.org>
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 A71E01201DB for <openpgp@ietfa.amsl.com>; Tue, 16 Apr 2019 14:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] 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 C7kaHmpqXM8G for <openpgp@ietfa.amsl.com>; Tue, 16 Apr 2019 14:36:56 -0700 (PDT)
Received: from smtpin.nadir.org (fry.nadir.org [217.114.68.218]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AD42120140 for <openpgp@ietf.org>; Tue, 16 Apr 2019 14:36:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtpin.nadir.org (Postfix) with ESMTP id 6DFFE7C97F0 for <openpgp@ietf.org>; Tue, 16 Apr 2019 23:36:52 +0200 (CEST)
Received: from smtpin.nadir.org ([127.0.0.1]) by localhost (fry.nadir.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OxvlsvTHW8Ux for <openpgp@ietf.org>; Tue, 16 Apr 2019 23:36:52 +0200 (CEST)
Received: from snail.zeromail.org (mail.zeromail.org [217.114.68.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtpin.nadir.org (Postfix) with ESMTPS id 379297C979C for <openpgp@ietf.org>; Tue, 16 Apr 2019 23:36:52 +0200 (CEST)
Received: from [127.0.0.1] (localhost [127.0.0.1])ng TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by snail.zeromail.org (Postfix) with ESMTPSA id 8754DBFC91 for <openpgp@ietf.org>; Tue, 16 Apr 2019 23:36:51 +0200 (CEST)
Date: Tue, 16 Apr 2019 23:36:49 +0200
From: ilf <ilf@zeromail.org>
To: openpgp@ietf.org
Message-ID: <20190416213649.GJ1226@zeromail.org>
Mail-Followup-To: openpgp@ietf.org
References: <87v9zt2y2d.fsf@fifthhorseman.net> <20190412201300.GJ1226@zeromail.org> <87ef635hmt.fsf@fifthhorseman.net> <20190416195614.GH1226@zeromail.org> <87h8ax3chy.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="w0nMBknB8iaaAbdO"
Content-Disposition: inline
In-Reply-To: <87h8ax3chy.fsf@fifthhorseman.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/HybijbkgnJLuvwF33tiSWB3dL-0>
Subject: Re: [openpgp] Modelling an abuse-resistant OpenPGP keyserver
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Apr 2019 21:36:59 -0000

Thanks for merging (and rebasing).

Daniel Kahn Gillmor:
> I think the next draft will use "certificate discovery" to refer only 
> to this third case, and will rename lookup-by-user-id to "certificate 
> lookup".  Does that make sense?

Yes, sounds good to me.

(Even if there are other ways of learning about a certificate 
fingerprint like https://tools.ietf.org/html/draft-mccain-keylist)

Thanks for your work!

-- 
ilf

If you upload your address book to "the cloud", I don't want to be in it.

v2.30.2 | Report a Bug | By Email | System Status