Re: [openpgp] Fingerprints and their collisions resistance

Nicholas Cole <nicholas.cole@gmail.com> Thu, 03 January 2013 09:33 UTC

Return-Path: <nicholas.cole@gmail.com>
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 880D321F8A6B for <openpgp@ietfa.amsl.com>; Thu, 3 Jan 2013 01:33:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KLtHjg7UiP7Q for <openpgp@ietfa.amsl.com>; Thu, 3 Jan 2013 01:33:28 -0800 (PST)
Received: from mail-vb0-f41.google.com (mail-vb0-f41.google.com [209.85.212.41]) by ietfa.amsl.com (Postfix) with ESMTP id B47C121F8A52 for <openpgp@ietf.org>; Thu, 3 Jan 2013 01:33:28 -0800 (PST)
Received: by mail-vb0-f41.google.com with SMTP id l22so14954291vbn.14 for <openpgp@ietf.org>; Thu, 03 Jan 2013 01:33:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=RF+K7+aAs6qi5ANBchQMYbQykFC2VaNFzBDZ2eDz3e4=; b=H3JgSo5IUc8dwGXKHxztPlTw3FmYDyZRcX9VTvAbuRemELsNCgRMi7KEGjE3tzYB9N bbr+/Jn1Bs+mEkeR0YwTwNwm7jRpUEsntcgcdVlk+8Ax+Em3d/AbjCxq0Rg5Tp652ItA 3oHiiXj+di9EsWMQkd7g0WyOXirNRJQC/ZXyPRxaJNFbF24ehf9KxXTiP7puu9wWsEIr PRb5wLuIXAPqQiCEPr772IHb0aTFiEvqGjORf+UYmTVc0fL+YgkK1FefX/MItXE9kV/I CmOkP08G+FP+TNpWcTNQOL3E0KmB5Dd8G6t3xjPa8ZKfMjo89PiWkGzU5z3wzk8Usg17 pcow==
MIME-Version: 1.0
Received: by 10.220.151.142 with SMTP id c14mr72484385vcw.16.1357205607728; Thu, 03 Jan 2013 01:33:27 -0800 (PST)
Received: by 10.58.37.40 with HTTP; Thu, 3 Jan 2013 01:33:27 -0800 (PST)
In-Reply-To: <50E530D6.6020609@brainhub.org>
References: <50E530D6.6020609@brainhub.org>
Date: Thu, 03 Jan 2013 09:33:27 +0000
Message-ID: <CAAu18hc87Qe3d0mCxzw5CpPRWv3i2YmZCB42sttRyyOtFD2jDw@mail.gmail.com>
From: Nicholas Cole <nicholas.cole@gmail.com>
To: Andrey Jivsov <openpgp@brainhub.org>
Content-Type: multipart/alternative; boundary="f46d043be06a22c47604d25f0e4a"
Cc: openpgp@ietf.org
Subject: Re: [openpgp] Fingerprints and their collisions resistance
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.12
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: Thu, 03 Jan 2013 09:33:29 -0000

On Thu, Jan 3, 2013 at 7:18 AM, Andrey Jivsov <openpgp@brainhub.org> wrote:

> We exchanged a few emails on gnupg list about this this issue, which I
> think belongs here, the OpenPGP thread.
>

[snip]

Public keys offer a reasonable opportunity to place arbitrary bytes into
> fields that are hashed. For example, DSA P,Q,G, are primes. Every byte but
> the last one of a 2048 bit prime can be fixed, on average, due to the high
> density of primes. It suggests that the task of finding a collision with
> public keys is at least no more difficult than for ASCII documents.
>

If anyone has already done this, they are keeping very quiet about it.

I don't think I favour interim solutions - it would be better if the issue
were tackled directly.  From a user point of view, it would be good if new
formats were decided that hard-wire a new formats.  I think that these
decisions should be made sooner rather than later, because it will take
some years for end-user software to fully catch up.  Is it impossible to
think that new standards would be decided this year?

One issue with SHA-3 is that the fingerprints are going to be very long.
 How should these be displayed to the user?  Hex strings seem unsuitable
for this task, and I think any new standard should recommend that
fingerprints be displayed in some other way - probably using a different
base.

Best wishes,

N.