Re: [openpgp] Question on WKD, Key Discovery

Paul Wouters <paul@nohats.ca> Thu, 09 May 2019 13:51 UTC

Return-Path: <paul@nohats.ca>
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 57A301200DB for <openpgp@ietfa.amsl.com>; Thu, 9 May 2019 06:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 4-LESOyURYB2 for <openpgp@ietfa.amsl.com>; Thu, 9 May 2019 06:51:23 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BCE971200C1 for <openpgp@ietf.org>; Thu, 9 May 2019 06:51:23 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 450FB20227zL5s; Thu, 9 May 2019 15:51:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1557409882; bh=Kb4qWmi4JFETe8h/KJqJ9hezD/CtQZfH8RZNY1xrFKo=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=m6g7HXtkzDhX6/9HkXW+1Z8Woh46GaFyPBsd/0/wbNrmgZWr+X0+NiMXdqXnMPc28 bB6/YZVahhVlXBt4p9ZoO26+nDIxWlYuJ4S8ZwbGIID6+auG35Cew30sqy4LqpiM1I geWINC9uYjLy9yhQVCZJ//131BVZJ1tUuSn0s8hE=
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 O-ljTFRkzWNn; Thu, 9 May 2019 15:51:20 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 9 May 2019 15:51:20 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 88EB85C853; Thu, 9 May 2019 09:51:19 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 88EB85C853
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 7FD8F43A0D6F; Thu, 9 May 2019 09:51:19 -0400 (EDT)
Date: Thu, 09 May 2019 09:51:19 -0400
From: Paul Wouters <paul@nohats.ca>
To: juga <juga@riseup.net>
cc: openpgp@ietf.org
In-Reply-To: <5ee04d6e-1039-e9d8-f9c5-8907910ec75a@riseup.net>
Message-ID: <alpine.LRH.2.21.1905090949590.21050@bofh.nohats.ca>
References: <5ee04d6e-1039-e9d8-f9c5-8907910ec75a@riseup.net>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/PYmqkGGqOVbzcjlXCsOB9pKD1LY>
Subject: Re: [openpgp] Question on WKD, Key Discovery
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: Thu, 09 May 2019 13:51:25 -0000

On Thu, 9 May 2019, juga wrote:

> The last version of the draft [0] states:
>
>  Only if the required sub-domain does not exist, they SHOULD
>  fall back to the direct method.
>
> Should implementations fall back to the direct method on any error
> trying to fetch the key with the advanced method and not just when the
> sub-domain doesn't exist?.

The SHOULD there is tricky. Unless you are using DNSSEC, the question
of "does a domain not exist" is very vulnerable to spoofing by an
attacker.

Paul