Re: [openpgp] New fingerprint: to v5 or not to v5

vedaal@nym.hush.com Thu, 17 September 2015 22:05 UTC

Return-Path: <vedaal@nym.hush.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 0EAC01A885F for <openpgp@ietfa.amsl.com>; Thu, 17 Sep 2015 15:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level:
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 UgKirC_RRNYI for <openpgp@ietfa.amsl.com>; Thu, 17 Sep 2015 15:05:37 -0700 (PDT)
Received: from smtp5.hushmail.com (smtp5.hushmail.com [65.39.178.142]) (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 D6C0B1A8821 for <openpgp@ietf.org>; Thu, 17 Sep 2015 15:05:36 -0700 (PDT)
Received: from smtp5.hushmail.com (localhost [127.0.0.1]) by smtp5.hushmail.com (Postfix) with SMTP id 719EC6026B for <openpgp@ietf.org>; Thu, 17 Sep 2015 22:05:36 +0000 (UTC)
X-hush-tls-connected: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=hush.ai; h=date:to:subject:from; s=hush; bh=Q+3gptW1p/y1t+Pi1p8J2hLMcw0B7/SKbq4/P+mmoP8=; b=bUMVwG2JszZaB9/ho4JmH7YqNM3fOx25bhpKSW+AmLc7qGv6bmpCZ2l6eKKqeDKfk18VB+vLKAbNTgfuC52ZRrQRWgaSEp/9EzIoOWt3NhI3zUM3I8jcQxEYzOenpp9LAQk1F9ad2h2Q5ONneM8A2YoG9gs6ldaxOey6n0qsd1x2O6gyPgKUK6XW79ApWA+VB/NfB3+pzmZUupmgOoj6ZHYn8YODqjqlD180bWH6qOuSabSvi5KrqTqT8/KUu3FkssCmwyzyOo1NBrS1JUIpDFwCFdFoBc4yxkMUm3d+jBI6MA45Xt6HnFIb3v3LLlocVl9MS2GD9xtzlI5hdQ1gkA==
Received: from smtp.hushmail.com (w3.hushmail.com [65.39.178.62]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp5.hushmail.com (Postfix) with ESMTPS for <openpgp@ietf.org>; Thu, 17 Sep 2015 22:05:36 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99) id 574C4C035D; Thu, 17 Sep 2015 22:05:36 +0000 (UTC)
MIME-Version: 1.0
Date: Thu, 17 Sep 2015 18:05:36 -0400
To: openpgp@ietf.org
From: vedaal@nym.hush.com
In-Reply-To: <878u84zy4r.fsf@vigenere.g10code.de>
Content-Type: multipart/alternative; boundary="=_06b944fe06bdebc164b5fa5ded257e8d"
Message-Id: <20150917220536.574C4C035D@smtp.hushmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/XmdZFBfpUQoctT3vQ42xURXf4xA>
Subject: Re: [openpgp] New fingerprint: to v5 or not to v5
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: <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: Thu, 17 Sep 2015 22:05:38 -0000


On 9/17/2015 at 2:44 PM, "Werner Koch"  wrote:
Some people claim that a SHA-1 fingerprint might soon be problematic
due
to collision attacks.  If we assume that this is indeed the case, the
question is whether switching to SHA-256 for the very same key does
actually help: The mix of different fingerprints for the same key will
lead to the same confusion we have seen with X.509 and ssh.  Further,
if
there is a need to switch to a stronger fingerprint format for the
same
key, should the user not also assume that the use of the key has
already
been compromised and it is time to create a new key?

=====

If Collision attacks become viable for SHA-1 fingerprints, then they
would probably also become viable for subkeys as well, and it might be
possible for an attacker to generate a subkey with a collision for the
cross-certifying signature, and be able to graft a false subkey onto a
master key with a SHA-1 signature, which would definitely be a key
compromise.

so, yes,  it would be reasonable to have a new V5 format for the new
fingerprint.
vedaal