Re: [openpgp] key distribution by email strategy

Steffen Nurpmeso <> Mon, 14 December 2020 21:20 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 384A13A12B0 for <>; Mon, 14 Dec 2020 13:20:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 905ZDZTpUEa9 for <>; Mon, 14 Dec 2020 13:20:30 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 5456D3A12AE for <>; Mon, 14 Dec 2020 13:20:29 -0800 (PST)
Received: by (Postfix, from userid 1000) id 8C61316057; Mon, 14 Dec 2020 22:20:26 +0100 (CET)
Date: Mon, 14 Dec 2020 22:20:26 +0100
From: Steffen Nurpmeso <>
To: John Scott <>
Message-ID: <>
In-Reply-To: <23083923.ouqheUzb2q@t450>
References: <> <> <> <23083923.ouqheUzb2q@t450>
Mail-Followup-To: John Scott <>,
User-Agent: s-nail v14.9.20-84-g7268a84d
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Subject: Re: [openpgp] key distribution by email strategy
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 14 Dec 2020 21:20:32 -0000


John Scott wrote in
 |On Saturday, December 12, 2020 5:08:25 PM EST Steffen Nurpmeso wrote:
 |> I'd rather have the same for OpenPGP, a signed message with the
 |> public thing extractable embedded, then i at least know that the
 |> signer had the private key for that public thing at hand.
 |I don't think it's standard but GnuPG enables this with the --include-key-
 |block and --auto-key-import pair of options:
 |> This  option  is  used to embed the actual signing key into a
 |> data signature.  The embedded key is stripped down to a
 |> single user id and includes only the signing subkey used to
 |> create the signature as well as as valid encryption subkeys. 
 |> All other info  is  removed from the key to keep it and thus
 |> the signature small.  This option is the OpenPGP counterpart
 |> to the gpgsm option --include-certs.
 |> This  is an offline mechanism to get a missing key for
 |> signature verification and for later encryption to this key. 
 |> If this option is enabled and a signature includes an
 |> embedded key, that key is used to verify the  signature  and 
 |> on  verification success that key is imported. The default is
 |> --no-auto-key-import.
 |> On  the  sender  (signing) site the option --include-key-block
 |> needs to be used to put the public part of the signing key as
 |> “Key Block subpacket” into the signature.

Very interesting!  I did not know that indeed, i am still with gpg
1.4 ;-), but gnupg 2.25 is standard in CRUX-Linux, too, so.
Yes, that is a very, very good thing then, in my opinion!
Begs the question, if i will implement OpenPGP support next year
(after the MIME rewrite that thing needs first), can i somehow
integrate this with email when using standard OpenPGP MIME format.

|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)