Re: [openpgp] Version 5 key and fingerprint proposal

KellerFuchs <KellerFuchs@hashbang.sh> Tue, 07 March 2017 23:06 UTC

Return-Path: <kellerfuchs@hashbang.sh>
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 84C831294C4 for <openpgp@ietfa.amsl.com>; Tue, 7 Mar 2017 15:06:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, 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 OK33JP_XF8tF for <openpgp@ietfa.amsl.com>; Tue, 7 Mar 2017 15:06:06 -0800 (PST)
Received: from mail.hashbang.sh (mail.hashbang.sh [104.236.46.93]) (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 CC29D129473 for <openpgp@ietf.org>; Tue, 7 Mar 2017 15:06:06 -0800 (PST)
Received: from localhost (to1.hashbang.sh [104.245.37.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.hashbang.sh (Postfix) with ESMTPS id D8BE916B8F for <openpgp@ietf.org>; Tue, 7 Mar 2017 23:06:05 +0000 (UTC)
Date: Tue, 07 Mar 2017 23:06:05 +0000
From: KellerFuchs <KellerFuchs@hashbang.sh>
To: openpgp@ietf.org
Message-ID: <20170307230605.GA2@hashbang.sh>
References: <87varlou5m.fsf@wheatstone.g10code.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <87varlou5m.fsf@wheatstone.g10code.de>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/CmDxp3k7AiRk7dQeQLdWq84fW0E>
Subject: Re: [openpgp] Version 5 key and fingerprint proposal
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
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, 07 Mar 2017 23:06:08 -0000

On Tue, Mar 07, 2017 at 06:48:05PM +0100, Werner Koch wrote:
> Hi!
> 
> Find my proposal for a V5 key and a new fingerprint scheme below and
> also with a colored diff at
> 
>   <https://gitlab.com/openpgp-wg/rfc4880bis/commit/ba4f884c6d5483071d6adbc1e43978b60980440a>

Thanks a lot for doing this.


> [...]
> =====
> From ba4f884c6d5483071d6adbc1e43978b60980440a Mon Sep 17 00:00:00 2001
> From: Werner Koch <wk@gnupg.org>
> Date: Tue, 7 Mar 2017 17:48:15 +0100
> Subject: [PATCH] Specify a v5 key version and a new fingerprint scheme.
> [...]
> ---
>  middle.mkd | 98 +++++++++++++++++++++++++++++++++++++++++++++++++++-----------
>  1 file changed, 81 insertions(+), 17 deletions(-)
> 
> diff --git a/middle.mkd b/middle.mkd
> index 462730b..1cd9f86 100644
> --- a/middle.mkd
> +++ b/middle.mkd
> @@ -1279,8 +1279,11 @@ #### {5.2.3.14} Regular Expression
>  
>  #### {5.2.3.15} Revocation Key
>  
> -(1 octet of class, 1 octet of public-key algorithm ID, 20 octets of
> -fingerprint)
> +(1 octet of class, 1 octet of public-key algorithm ID, 20 or 25 octets
> +of fingerprint)
> +
> +V4 keys use the untruncated 20 octet fingerprint; V5 keys use the
> +right truncated 25 octet fingerprint

This is the first occurence of “right truncated”, as far as I can tell.

Since it's not entirely clear (at least to me) if this means keeping the 20
rightmost octets or dropping octets right of the 25th, not introducing it
is not ideal.

Furthermore, this hints at there being a left-truncation too, and having
both seems like a source of confusion. What about simply calling this “the
truncated 25-octets fingerprint” ?


Also, but I likely missed the relevant WG thread, why truncate the
fingerprint to 200 bits? (Not that this is likely an issue.)


Best,

  kf