Re: [openpgp] Followup on fingerprints

ianG <iang@iang.org> Sat, 01 August 2015 00:54 UTC

Return-Path: <iang@iang.org>
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 D31551ACEA2 for <openpgp@ietfa.amsl.com>; Fri, 31 Jul 2015 17:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 SCcFWUOd6dSZ for <openpgp@ietfa.amsl.com>; Fri, 31 Jul 2015 17:54:06 -0700 (PDT)
Received: from virulha.pair.com (virulha.pair.com [209.68.5.166]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AAD21ACE96 for <openpgp@ietf.org>; Fri, 31 Jul 2015 17:53:22 -0700 (PDT)
Received: from tormenta.local (iang.org [209.197.106.187]) by virulha.pair.com (Postfix) with ESMTPSA id EC12F6D749; Fri, 31 Jul 2015 20:53:20 -0400 (EDT)
Message-ID: <55BC187F.1070300@iang.org>
Date: Sat, 01 Aug 2015 01:53:19 +0100
From: ianG <iang@iang.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: openpgp@ietf.org
References: <CAMm+LwgTcn8CY+Zk-f9gzXQtMJezG97T+kx2=C7PR5g7zFer_A@mail.gmail.com> <87twsn2wcz.fsf@vigenere.g10code.de> <CAMm+LwgRJX-SvydmpUAJMmN3yysi4zzGSpO2yY4JAMhD-9xLgQ@mail.gmail.com> <87si870zqy.fsf@vigenere.g10code.de>
In-Reply-To: <87si870zqy.fsf@vigenere.g10code.de>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/4JUenCsRq5ouvd20LS-Xear_Yac>
Subject: Re: [openpgp] Followup on fingerprints
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: Sat, 01 Aug 2015 00:54:08 -0000

On 29/07/2015 16:06 pm, Werner Koch wrote:
> On Wed, 29 Jul 2015 16:31, phill@hallambaker.com said:
>
>> On Wed, Jul 29, 2015 at 4:37 AM, Werner Koch <wk@gnupg.org> wrote:
>
>>> OpenPGP does not specify a user interface but the wire format.
>>> Obviously we use the most compact format there which is the plain binary
>>> format.  The questions are
>>>
>>
>> That is how we used to work in the 1990s. Since then we have had to do
>> internationalization and such.
>
> I can't see what internationalization has to do with the binary
> representation of a fingerprint.  As I said RFC-4880 is about the wire
> format and not about user interfaces: It tells how to compute a
> fingerprint and that it is the 16 octet MD5 hash or the 20 octet SHA-1
> hash.  Now that a fingerprint is printed like this
>
> pub   dsa2048/F2AD85AC1E42B367 2007-12-31 [expires: 2018-12-31]
>        Key fingerprint = 8061 5870 F5BA D690 3336  86D0 F2AD 85AC 1E42 B367
>
> is the choice of the concrete implementation.  It is an interesting idea
> to have a common way of representing fingerprints to the user or in an
> URL but that is not in the scope of RFC-4800bis.


I thought we were agreed on all that and there was a separate draft that 
PHB had written that just covered fingerprints for the user?

Ie, we've cut this out of 4880(bis) because it has merit but it doesn't 
belong there.



iang (mystified, am I imagining this separate document?)