Re: [openpgp] Fingerprints
"Neal H. Walfield" <neal@walfield.org> Mon, 28 November 2022 14:40 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 5533EC14F749 for <openpgp@ietfa.amsl.com>; Mon, 28 Nov 2022 06:40:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8g0UAP7kEaVd for <openpgp@ietfa.amsl.com>; Mon, 28 Nov 2022 06:40:23 -0800 (PST)
Received: from mail.dasr.de (mail.dasr.de [202.61.250.5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8953AC14F743 for <openpgp@ietf.org>; Mon, 28 Nov 2022 06:40:23 -0800 (PST)
Received: from p5de92f23.dip0.t-ipconnect.de ([93.233.47.35] helo=forster.huenfield.org) by mail.dasr.de with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <neal@walfield.org>) id 1ozfIy-0004J0-M1; Mon, 28 Nov 2022 15:40:20 +0100
Received: from grit.huenfield.org ([192.168.20.9] helo=grit.walfield.org) by forster.huenfield.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <neal@walfield.org>) id 1ozfIx-00Dw6y-Lt; Mon, 28 Nov 2022 15:40:20 +0100
Date: Mon, 28 Nov 2022 15:40:19 +0100
Message-ID: <87o7sr5ei4.wl-neal@walfield.org>
From: "Neal H. Walfield" <neal@walfield.org>
To: Daniel Huigens <d.huigens@protonmail.com>
Cc: Derek Atkins <derek@ihtfp.com>, IETF OpenPGP WG <openpgp@ietf.org>
In-Reply-To: <6xCNnhcpeWwYU8Oe4cip1FRizpJDY0dWeNKaV0kccb2dDSIXBxxa-ir_KlXdE16235NZ-b6eQHlwBD-hrZkXnBuROlz904BVgtRXVp2eWlo=@protonmail.com>
References: <87cz9bt42n.wl-neal@walfield.org> <8a5ef78f325e70a71f54d0edae8d0bd0.squirrel@mail2.ihtfp.org> <6xCNnhcpeWwYU8Oe4cip1FRizpJDY0dWeNKaV0kccb2dDSIXBxxa-ir_KlXdE16235NZ-b6eQHlwBD-hrZkXnBuROlz904BVgtRXVp2eWlo=@protonmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (Gojō) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (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"
X-SA-Exim-Connect-IP: 192.168.20.9
X-SA-Exim-Mail-From: neal@walfield.org
X-SA-Exim-Scanned: No (on forster.huenfield.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/G1sZD3QYrEUjoI8d8fUztDIUvBc>
Subject: Re: [openpgp] Fingerprints
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 28 Nov 2022 14:40:24 -0000
On Fri, 25 Nov 2022 18:14:33 +0100, Daniel Huigens wrote: > On Friday, November 25th, 2022 at 17:02, Neal H. Walfield <neal@walfield.org> wrote: > > Second, we could just make the version number part of the fingerprint. > > That is, the fingerprint could be defined as the concatenation of 6 > > (assuming we do s/v5/v6/) plus the 256-bit SHA2-256 hash. > > I would be in favor of always specifying the key version and fingerprint > together. The one worry I have about making it actually part of the > fingerprint is that if people are doing manual fingerprint verification > (which, I'm the first to say they shouldn't, but..) then the leading > constant 6 may make it easier to make two fingerprints appear "similar". > > We could simply state that v6 key fingerprints should be presented as > 6:xxxx..., for example, to make it clearer what's going on. That way, > we can maybe also roll it out for v4 fingerprints, and always show > v:fingerprint without causing too much confusion, hopefully. I understand the motivation, but I'd rather hide this information; it's an implementation detail that users don't need to know about. If we start showing users 4:xxx, they are going to be confused. Moreover, old software won't understand what to do with it. Neal
- [openpgp] Fingerprints Neal H. Walfield
- Re: [openpgp] Fingerprints Derek Atkins
- Re: [openpgp] Fingerprints Daniel Huigens
- Re: [openpgp] Fingerprints Neal H. Walfield
- Re: [openpgp] Fingerprints Neal H. Walfield
- Re: [openpgp] Fingerprints Neal H. Walfield