Re: [Secdispatch] Deterministic generation of public key pairs

Michael Richardson <> Tue, 10 March 2020 17:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 726243A1652 for <>; Tue, 10 Mar 2020 10:28:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id T_LiuHNX4TK0 for <>; Tue, 10 Mar 2020 10:28:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 77E523A1659 for <>; Tue, 10 Mar 2020 10:28:04 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id D4AC43818F; Tue, 10 Mar 2020 13:26:46 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by (Postfix) with ESMTP id CD268825; Tue, 10 Mar 2020 13:27:58 -0400 (EDT)
From: Michael Richardson <>
To: Phillip Hallam-Baker <>
cc: IETF SecDispatch <>
In-Reply-To: <>
References: <>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 10 Mar 2020 13:27:58 -0400
Message-ID: <13723.1583861278@localhost>
Archived-At: <>
Subject: Re: [Secdispatch] Deterministic generation of public key pairs
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 10 Mar 2020 17:28:10 -0000

Phillip Hallam-Baker <> wrote:
    > udf config ssh-agent ZAAA-FFQA-3LE5-SAHG-E6K6-HOTN-TVLB-K4A

    > This is a seed that can be written down and can be used to generate a
    > private keypair using any of the commonly used public key algorithms. So
    > you can use it for any application where you would use traditional key
    > escrow.

    > One thing I use this for is to move S/MIME and PGP keys about. Can also use
    > it to keep a paper back up of whole disk encryption keys etc.

    > The spec (but not the tool yet) also supports Shamir Secret Sharing. I need
    > to rejig that to match the developments in the threshold spec.

    > So is this something we should do and if so where? This is separable from
    > the Mesh and does have some functionality overlap. But it also makes a lot
    > of common sysadmin config much easier.

I think AD sponsorship for the entire UDF document.
(Not just the deterministic key generation part. or was that part of your goal?)

A better name is needed, as there has been snakeoil created that had a
similar name.

Michael Richardson <>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-