[openpgp] Non-SHA-1 fingerprints in signatures [was: Proposal for a separable ring signature scheme...]

Vincent Yu <v@v-yu.com> Fri, 14 March 2014 01:28 UTC

Return-Path: <v@v-yu.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FAD31A07DA for <openpgp@ietfa.amsl.com>; Thu, 13 Mar 2014 18:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 dqVPXi1Z-cjf for <openpgp@ietfa.amsl.com>; Thu, 13 Mar 2014 18:28:26 -0700 (PDT)
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135]) by ietfa.amsl.com (Postfix) with ESMTP id 4504D1A07D9 for <openpgp@ietf.org>; Thu, 13 Mar 2014 18:28:26 -0700 (PDT)
Received: from smtp1.hushmail.com (localhost [127.0.0.1]) by smtp1.hushmail.com (Postfix) with SMTP id A915040176 for <openpgp@ietf.org>; Fri, 14 Mar 2014 01:28:19 +0000 (UTC)
Received: from smtp.hushmail.com (w4.hushmail.com [65.39.178.50]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp1.hushmail.com (Postfix) with ESMTPS; Fri, 14 Mar 2014 01:28:19 +0000 (UTC)
Message-ID: <3e9143bf60d2252a67149eb4b984bcdb@smtp.hushmail.com>
Date: Thu, 13 Mar 2014 21:28:15 -0400
From: Vincent Yu <v@v-yu.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Jon Callas <jon@callas.org>
References: <80674820640dbeb5ae81f81c67d87541@smtp.hushmail.com> <23C2DE82-93B7-48A6-95A6-14B4F5DD1F42@callas.org>
In-Reply-To: <23C2DE82-93B7-48A6-95A6-14B4F5DD1F42@callas.org>
X-Enigmail-Version: 1.6
OpenPGP: id=d28d7c4078b3742a; url=https://v-yu.com/pubkeys/openpgp.asc
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="MxxdxCobXVElxkEKGTGc4ifJdXSDDCQsp"
Archived-At: http://mailarchive.ietf.org/arch/msg/openpgp/bnlFNB2aXTUTPNQNd9aHsosUdL8
Cc: openpgp@ietf.org
Subject: [openpgp] Non-SHA-1 fingerprints in signatures [was: Proposal for a separable ring signature scheme...]
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 14 Mar 2014 01:28:28 -0000

On 03/13/2014 06:02 PM, Jon Callas wrote:
> My suggestion is that you write up an I-D, and push it.
>
> My quick read looks like this is a useful thing, and it would be nice to have. Just as Andrey pushed an ECC draft and there have been others, it'd be a great way to go.
>
> As DKG noted, we have a constant collision, but that's not a big deal. That's why we have IANA.
>
> 	Jon

Thanks for your comments. I plan to write up and submit an I-D if no one 
points out egregious problems with the current proposal.

In past threads, there were discussions about supporting non-SHA-1 
fingerprints [1] and including full issuer fingerprints in signatures 
[2]. You forwarded to this list a proposal for a new fingerprint [3]. 
Did anything concrete come out of that proposal or other discussions?

In my proposal, I am using key IDs (i.e., the rightmost 8 octets of 
SHA-1 fingerprints) in a new signature subpacket, but I would like to 
switch to non-SHA-1 fingerprints if there is a standard or consensus 
about how they should be formatted. This is an opportune time to 
introduce such fingerprints since backward compatibility is not a 
relevant consideration.

Comments on this are welcome from everyone.

Vincent

[1]: https://www.ietf.org/mail-archive/web/openpgp/current/msg00253.html
[2]: https://www.ietf.org/mail-archive/web/openpgp/current/msg00405.html
[3]: https://www.ietf.org/mail-archive/web/openpgp/current/msg00259.html