[openpgp] Optional User IDs

"Neal H. Walfield" <neal@walfield.org> Fri, 31 May 2019 12:27 UTC

Return-Path: <neal@walfield.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 17BC11200B2 for <openpgp@ietfa.amsl.com>; Fri, 31 May 2019 05:27:22 -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, SPF_NONE=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 nujnu216BQy7 for <openpgp@ietfa.amsl.com>; Fri, 31 May 2019 05:27:20 -0700 (PDT)
Received: from mail.dasr.de (mail.dasr.de [217.69.77.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF75B1200A1 for <openpgp@ietf.org>; Fri, 31 May 2019 05:27:19 -0700 (PDT)
Received: from p54b1e8be.dip0.t-ipconnect.de ([84.177.232.190] helo=chu.huenfield.org.walfield.org) by mail.dasr.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from <neal@walfield.org>) id 1hWgcu-0002gW-84; Fri, 31 May 2019 12:27:17 +0000
Date: Fri, 31 May 2019 14:27:15 +0200
Message-ID: <875zpqg670.wl-neal@walfield.org>
From: "Neal H. Walfield" <neal@walfield.org>
To: Vincent Breitmoser <look@my.amazin.horse>
Cc: openpgp@ietf.org
In-Reply-To: <3LBKVNEMXC3DV.3JS3W5ZE7TFEZ@my.amazin.horse>
References: <3LBKVNEMXC3DV.3JS3W5ZE7TFEZ@my.amazin.horse>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/eiEwNC2SVtEgNFRRcM0NtZEepWM>
Subject: [openpgp] Optional User IDs
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: Fri, 31 May 2019 12:27:22 -0000

At Fri, 31 May 2019 09:42:21 +0200,
Vincent Breitmoser wrote:
> However, despite this flexibility, there are shortcomings for the use case of
> distributing these updates in a privacy-preserving way:
> 
> 1. A TPK must consist of a primary key, followed by at least one UserID.
> Strictly speaking there doesn't have to be a signature on that User ID, but in
> practice OpenPGP implementations commonly consider TPKs that carry no UserID (or
> no signed UserID) as invalid.

My understanding is that this restriction has been lifted from 4880bis
for V4 keys.  Specifically, Section 12.1 now makes User IDs optional:

  Primary-Key
     [Revocation Self Signature]
     [Direct Key Signature...]
     [User ID [Signature ...] ...]

  https://datatracker.ietf.org/doc/draft-ietf-openpgp-rfc4880bis/?include_text=1

Whereas in 4880, this reads:

  Primary-Key
      [Revocation Self Signature]
      [Direct Key Signature...]
       User ID [Signature ...]
      [User ID [Signature ...] ...]

  https://tools.ietf.org/html/rfc4880#section-12.1

As I understand it, this change comes from merging
draft-atkins-openpgp-device-certificates, which says:

   The description in RFC 4880 requires a User ID.  Implementors of
   this specification can loosen that requirement such that an
   augmented V4 device certificate looks like the following sequence
   (no longer requiring a User ID packet):

   https://datatracker.ietf.org/doc/draft-atkins-openpgp-device-certificates/?include_text=1,

:) Neal