IETF Logo Mail Archive

Re: [openpgp] Fingerprints and their collisions resistance

Bill Frantz <frantz@pwpconsult.com> Sun, 06 January 2013 17:29 UTC

Return-Path: <frantz@pwpconsult.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 8F87F21F84FD for <openpgp@ietfa.amsl.com>; Sun, 6 Jan 2013 09:29:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 VPRC2K9OHLdu for <openpgp@ietfa.amsl.com>; Sun, 6 Jan 2013 09:29:12 -0800 (PST)
Received: from elasmtp-junco.atl.sa.earthlink.net (elasmtp-junco.atl.sa.earthlink.net [209.86.89.63]) by ietfa.amsl.com (Postfix) with ESMTP id C1D8521F84F5 for <openpgp@ietf.org>; Sun, 6 Jan 2013 09:29:11 -0800 (PST)
Received: from [173.75.83.83] (helo=Williams-MacBook-Pro.local) by elasmtp-junco.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <frantz@pwpconsult.com>) id 1Tru22-0004p5-B5; Sun, 06 Jan 2013 12:29:10 -0500
Date: Sun, 06 Jan 2013 09:29:10 -0800
From: Bill Frantz <frantz@pwpconsult.com>
To: Andrey Jivsov <openpgp@brainhub.org>
X-Priority: 3
In-Reply-To: <50E91770.3050203@brainhub.org>
Message-ID: <r422Ps-1075i-C3E035131DAD4703BFE50BF321F7EDA1@Williams-MacBook-Pro.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Mailsmith 2.3.1 (422)
X-ELNK-Trace: 3a5e54fa03f1b3e21aa676d7e74259b7b3291a7d08dfec7942a4a2d03d544dc3d70467dcfd94a494350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 173.75.83.83
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: Sun, 06 Jan 2013 17:29:12 -0000

On 1/5/13 at 10:19 PM, openpgp@brainhub.org (Andrey Jivsov) wrote:

>There is an objective need to ID the key material with a hash. 
>I think at the very least we should spec the algorithm in an 
>e-mail on this list. It would even be better if this algorithm 
>was supported across applications, so that the IDs are portable.

I hope that anything which affects program interoperability or 
escapes to the user would be specified in a more permanent way 
than an email to a list. An informational RFC might be the easy choice.

Cheers - Bill

---------------------------------------------------------------------------
Bill Frantz        |"We used to quip that "password" is the most common
408-356-8506       | password. Now it's 'password1.' Who said 
users haven't
www.pwpconsult.com | learned anything about security?" -- Bruce Schneier

v2.23.0 | Report a Bug | By Email