Re: [openpgp] Fingerprints

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 27 April 2015 20:57 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 199681A8A7F for <openpgp@ietfa.amsl.com>; Mon, 27 Apr 2015 13:57:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.278
X-Spam-Level:
X-Spam-Status: No, score=-3.278 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, GB_I_LETTER=-2, 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 OMQZ35EC7mKD for <openpgp@ietfa.amsl.com>; Mon, 27 Apr 2015 13:57:42 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (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 4E5F01A88FE for <openpgp@ietf.org>; Mon, 27 Apr 2015 13:57:42 -0700 (PDT)
Received: by lbbuc2 with SMTP id uc2so91982414lbb.2 for <openpgp@ietf.org>; Mon, 27 Apr 2015 13:57:40 -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:content-type; bh=XlOF89a5S2fOt/WSjjPVwsyOctafo0Xp8Oiw97qD2TM=; b=VdEDvai/29ioVdJS+IatkC9lD8y25ELjtzUwG4PVF6w6iZpPATso7j0+oFy2jFvYUM vHOnjdQzLLNyqWqwaXwKIIhwNADTewnis9xHdEbBtgFYzsBWMwv+MPQH8BMMRQwwHSuC GDYjXiJ4d7/NVkL+K2Olquoi+vSKx+Id3wYFio4ionpzCHHuGRS8Hl18PfocC1d3/+uD 35g58N9sE+CEHMN5TeMo95FMebnN7yZyCqYKbFwLzIQ0rbc0E81XgaTKne0Zs5+sRUhI FQtscbF4xwe4jLm8G5T6h2+w+eIfAqd5YGuz2qkBilg6lx5m5+NOWU3682HnFIGPCrI/ tqgA==
MIME-Version: 1.0
X-Received: by 10.152.45.97 with SMTP id l1mr11900979lam.55.1430168260866; Mon, 27 Apr 2015 13:57:40 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.203.163 with HTTP; Mon, 27 Apr 2015 13:57:40 -0700 (PDT)
In-Reply-To: <87wq0xb99x.fsf@vigenere.g10code.de>
References: <CAMm+LwhbB+-MnGRBCvprgAGOuu+5CJ2rgod7EBGOQR5UNVrspQ@mail.gmail.com> <87d232lkb6.fsf@alice.fifthhorseman.net> <87618qzlw0.fsf@vigenere.g10code.de> <1429922578.4659.49.camel@scientia.net> <1DC3C8C67280FB4C9A402CB6DB1358F519E90A4A32@S2008SBS.intern.giepa.de> <87pp6pczgq.fsf@vigenere.g10code.de> <CAMm+Lwh90BtUkVFvxk4y+PA0onW_2ixnoFEnxsgVoh3=jGcgUA@mail.gmail.com> <87wq0xb99x.fsf@vigenere.g10code.de>
Date: Mon, 27 Apr 2015 16:57:40 -0400
X-Google-Sender-Auth: w2ceBoskp4eh1bHibntXNUu7Bmo
Message-ID: <CAMm+LwgUrSxRfWQWSkgEe3reUxuqNU8GYsDbqjhq7aU=OV14Gg@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>, Daniel Ranft <Daniel.Ranft@giepa.de>, Christoph Anton Mitterer <calestyo@scientia.net>, "openpgp@ietf.org" <openpgp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/Mc8Mq8nO0dJ5sDyHcA8XGJ43gNg>
Subject: Re: [openpgp] 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: <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: Mon, 27 Apr 2015 20:57:50 -0000

On Mon, Apr 27, 2015 at 4:34 PM, Werner Koch <wk@gnupg.org> wrote:
> On Mon, 27 Apr 2015 19:58, phill@hallambaker.com said:
>
>>> work reliable for mass deployment.  Thus for backing up and syncing
>>> private keys they use a letters and digits based code to seed a PRNG.
>>
>> I can't see the point of that.
>
> The point is that typing
>
>   A3HT-378G-WE7Q-....
>
> works more reliable than scanning QR codes.
>
>> Encrypt the private key(s) under a symmetric key, split the symmetric
>> key into as many shares as you need. Print out the key shares on paper
>
> Nobody talked about key splitting.

It can be added to either.

The difference between the approaches is as follows

With generation from seed we take a secret s and then generate K(s)
which requires the generation of the key to be completely
standardized.

With encryption of the private key we generate and dispose of a random
number p and use it as a seed, generate K(p) and then archive an
encrypted version under symmetric key s.


I prefer the second reason because it can be applied to any public key
algorithm and does not require a specific generation approach. Now
admittedly when we get to ECC algorithms, generation is not exactly
complicated.