Re: [dane] PGP security models, was Summary of IETF LC for draft-ietf-dane-openpgpkey

Paul Wouters <paul@nohats.ca> Tue, 22 September 2015 15:11 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5D81A90E1; Tue, 22 Sep 2015 08:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zQlHRLNzRHVd; Tue, 22 Sep 2015 08:11:20 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1107B1A9240; Tue, 22 Sep 2015 08:11:16 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3nL5gk1hSbz3CT; Tue, 22 Sep 2015 17:11:14 +0200 (CEST)
Authentication-Results: mx.nohats.ca; dkim=pass (1024-bit key) header.d=nohats.ca header.i=@nohats.ca header.b=OQPLq3vs
X-OPENPGPKEY: Message passed unmodified
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 2_HCdIXJkZrU; Tue, 22 Sep 2015 17:11:13 +0200 (CEST)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Tue, 22 Sep 2015 17:11:13 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 87B49800B0; Tue, 22 Sep 2015 11:11:12 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1442934672; bh=KfuxHPDRAXR07a6xHGTSHZpFBLqGhn1UKPaFyShu8hs=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=OQPLq3vsdHo7UJXbZusJRKoviBTwVqZV6SrYkkVAh42W+Ogr+kfvQP0cOHuAaQi+D PnKXQ1siEIkV0efHODiKA0Pa9wJuZZ50FstsIvXTw5gGTwxwafLM7hcFLoB94M0fbO CzFbr6o6EAKHrCIii8xvEqfIl0TCke/U6IOKgpxw=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.15.2/8.15.2/Submit) with ESMTP id t8MFBBjU005820; Tue, 22 Sep 2015 11:11:12 -0400
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Tue, 22 Sep 2015 11:11:11 -0400
From: Paul Wouters <paul@nohats.ca>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <754374D2DB528FC99BE470A8@JcK-HP8200.jck.com>
Message-ID: <alpine.LFD.2.20.1509221108280.4663@bofh.nohats.ca>
References: <20150921172109.19893.qmail@ary.lan> <alpine.LFD.2.20.1509211455150.420@bofh.nohats.ca> <754374D2DB528FC99BE470A8@JcK-HP8200.jck.com>
User-Agent: Alpine 2.20 (LFD 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/9dQoiddNFNfgW8CGE8TS-E7eqbU>
Cc: ietf@ietf.org, dane WG list <dane@ietf.org>
Subject: Re: [dane] PGP security models, was Summary of IETF LC for draft-ietf-dane-openpgpkey
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Sep 2015 15:11:21 -0000

On Tue, 22 Sep 2015, John C Klensin wrote:

> However, if you believe that, because of trust issues, people
> get keys only from personal contacts rather than indirectly from
> public databases, why are we discussing yet another public
> database-based approach?   Or are you convinced that the problem
> with the other public databases is that the DNS is inherently
> better for some reason such as the inability of third parties
> not associated with the domain in the address to add keys?

Yes.

The other common use problem is not being able to delete keys, so you end
up using a keyserver, get a (verified by WoT) key and then in response
you get a plaintext message saying "I forgot my passphrase so i cannot
delete/revoke my old key". With DNS, you can remove the key from DNS
without needing the private key or passphrase to it.

Paul