aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorWerner Koch <[email protected]>2025-11-16 17:51:07 +0000
committerWerner Koch <[email protected]>2025-11-16 17:53:32 +0000
commit8ceace31cc0551793a95e4d7acacc9d8de4ab28f (patch)
treeccc6dc4bd5e8cbaaeff8cc89b2bb152a569ec3ae
parentgpg: Allow the import of Kyber secret keys. (diff)
downloadgnupg-8ceace31cc0551793a95e4d7acacc9d8de4ab28f.tar.gz
gnupg-8ceace31cc0551793a95e4d7acacc9d8de4ab28f.zip
doc: Explain the export format of Kyber keys.
--
-rw-r--r--doc/gpg.texi9
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/gpg.texi b/doc/gpg.texi
index 2f9134252..7b41f9318 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -482,6 +482,15 @@ GnuPG may ask you to enter the passphrase for the key. This is
required, because the internal protection method of the secret key is
different from the one specified by the OpenPGP protocol.
+To support Kyber keys, which are implemented as a composite key along
+with an ECC key (aka PQ/T hybrid key), a GNU specific protocol
+extension is used. This allows the use of a smartcard for just one
+part of such a composite key. A re-encryption to an internal format
+is not needed as the keys restored in the very same way as GnuPG
+stores them. This extension may also be forced for all key types
+using the option @option{--export-options=mode1003}.
+
+
@item --export-ssh-key
@opindex export-ssh-key
This command is used to export a key in the OpenSSH public key format.