Re: [openpgp] Followup on fingerprints

Phillip Hallam-Baker <phill@hallambaker.com> Sat, 01 August 2015 01:49 UTC

Return-Path: <hallam@gmail.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 C9E881A6F0A for <openpgp@ietfa.amsl.com>; Fri, 31 Jul 2015 18:49:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 XMg_dCdebwrl for <openpgp@ietfa.amsl.com>; Fri, 31 Jul 2015 18:49:10 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 057451A6EE6 for <openpgp@ietf.org>; Fri, 31 Jul 2015 18:49:10 -0700 (PDT)
Received: by lbqc9 with SMTP id c9so29868774lbq.1 for <openpgp@ietf.org>; Fri, 31 Jul 2015 18:49:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1nEDga4uriPCCRv08i027hYXl/aIqOJvKlj1sSH+/Vw=; b=A39UE+zQEwgnI3ja4GD68h828ArcC+pNULmd8zMtQWeajS9qoEBMNyaVvh2gi3yz3J a7RVm8SFMTRCZp+f4IMmziuY2h4XOEkign7iwuv6tpZc0792eft+F6HxL2hPA3fbwNdo x0X27BTWRieplcVg8g3dAY4UmLqtmx3OS0o43yJQV79NBtDdtJDGlMAHY4A382LZasZO sR35puhHm1iywmZpomXepdJVzeIyHvIG9ZaLbA5L53RQzr1mKfNkFPPVEtPKoW4QP/X8 cMdiE+xkFlf2hMyEgP0AhDs/TB3jJe7A7Ebosu9PQYYLKTJnQ2LzW/6LFhypC5X9mm4C xHyg==
MIME-Version: 1.0
X-Received: by 10.112.126.42 with SMTP id mv10mr6498580lbb.58.1438393748462; Fri, 31 Jul 2015 18:49:08 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Fri, 31 Jul 2015 18:49:08 -0700 (PDT)
In-Reply-To: <55BC187F.1070300@iang.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> <55BC187F.1070300@iang.org>
Date: Fri, 31 Jul 2015 21:49:08 -0400
X-Google-Sender-Auth: 6xnoCzvNQxzx5Lw2ndPmSKeGA1M
Message-ID: <CAMm+Lwhrg3Vxmt_GE9vgLW62svujLLBK94SRWFC3EADYc_6KWw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: ianG <iang@iang.org>
Content-Type: multipart/alternative; boundary="001a11c36bc66ca46b051c362462"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/murNUAUX-Kjkp2oHDMuvV3vrfjU>
Cc: IETF OpenPGP <openpgp@ietf.org>
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 01:49:12 -0000

On Fri, Jul 31, 2015 at 8:53 PM, ianG <iang@iang.org> wrote:

> 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?)


You are riight.

https://tools.ietf.org/html/draft-hallambaker-udf-00

I will rename the next one with OpenPGP in the title so the search tools
can find it. The plan is a separate document that essentially only tracks
stuff related to OpenPGP but can be built on by others elsewhere.