Re: [perpass] OpenPGP mail/news header

Simon Josefsson <simon@josefsson.org> Thu, 28 August 2014 19:26 UTC

Return-Path: <simon@josefsson.org>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D0E1A0196 for <perpass@ietfa.amsl.com>; Thu, 28 Aug 2014 12:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.429
X-Spam-Level:
X-Spam-Status: No, score=-0.429 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001, URI_HEX=1.122] autolearn=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 FRAbDq1hxwq6 for <perpass@ietfa.amsl.com>; Thu, 28 Aug 2014 12:26:22 -0700 (PDT)
Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b0:1:1702::100]) (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 9D4A41A00D6 for <perpass@ietf.org>; Thu, 28 Aug 2014 12:26:21 -0700 (PDT)
Received: from latte.josefsson.org (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by duva.sjd.se (8.14.4/8.14.4/Debian-4) with ESMTP id s7SJQGC3016619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 28 Aug 2014 21:26:17 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Paul Wouters <paul@nohats.ca>
References: <20140828160043.76ae962f@latte.josefsson.org> <alpine.LFD.2.10.1408281046090.17182@bofh.nohats.ca>
OpenPGP: id=54265E8C; url=http://josefsson.org/54265e8c.txt
X-Hashcash: 1:22:140828:perpass@ietf.org::ME3HyRODNFL19Uib:2eC3
X-Hashcash: 1:22:140828:paul@nohats.ca::h6+kSmisqVRTq0Rn:LzdY
Date: Thu, 28 Aug 2014 21:26:15 +0200
In-Reply-To: <alpine.LFD.2.10.1408281046090.17182@bofh.nohats.ca> (Paul Wouters's message of "Thu, 28 Aug 2014 10:54:20 -0400 (EDT)")
Message-ID: <87bnr4za94.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130011 (Ma Gnus v0.11) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.98.4 at duva.sjd.se
X-Virus-Status: Clean
Archived-At: http://mailarchive.ietf.org/arch/msg/perpass/SC720qBTM19qiLFyBAAiQB2-rqE
Cc: perpass@ietf.org
Subject: Re: [perpass] OpenPGP mail/news header
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Aug 2014 19:26:24 -0000

Paul Wouters <paul@nohats.ca> writes:

> On Thu, 28 Aug 2014, Simon Josefsson wrote:
>
>> I have updated a six (!) year old document describing the OpenPGP
>> mail/news header field.  As it encourages and promotes use of
>> encrypted/signed email, I thought it would be relevant to this list.
>> All feedback is appreciated, either directly to me or here.
>>
>> http://tools.ietf.org/html/draft-josefsson-openpgp-mailnews-header-07
>
> I think it would be better to announce both keyid and fingerprint.
>
> Would it be better to use the longer keyid version?

Both key id and full fingerprint are permitted.

> Should a warning be added to the Security Considerations about v3 keys
> being vulnerable to forging of fingerprints?
> See: https://github.com/coruus/cooperpair/tree/master/keysteak

There is already the following text:

   Version 3 OpenPGP keys can be created with a chosen key id (aka "the
   0xDEADBEEF attack").  Verifying the Key ID of a retrieved key against
   the one provided in the field is thus not sufficient to protect
   against a man-in-the-middle attack.  Instead, the web-of-trust
   mechanism should be used.

> It would be nice to support OPENPGPKEY DNS records in header as well?
>
> either:
>
> OpenPGP: dns:paul@nohats.ca
>
> or
>
> OpenPGP:
> dns=ab16de0656382d91838914109ab89a0a4e04321550a1a20ace7a8b66._openpgpkey.nohats.ca

Should already be supported through RFC 4501, or am I missing something?

OpenPGP: id=12345678; url=dns:ab16de0656382d91838914109ab89a0a4e04321550a1a20ace7a8b66._openpgpkey.nohats.ca?TYPE=OPENPGPKEY

OpenPGP: id=12345678; url=dns:simon.josefsson.org?TYPE=CERT

> Perhaps add a reference to:
>
> http://tools.ietf.org/html/draft-wouters-dane-openpgp

Please propose some text to give the reference some context, and I'll
consider it. :-)

/Simon