summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJames Bottomley <James.Bottomley@HansenPartnership.com>2021-03-12 16:59:17 +0100
committerWerner Koch <wk@gnupg.org>2021-03-12 19:24:37 +0100
commit4997838c7b8f56be898e86a9b51f1e7fe5dca6d3 (patch)
treeef5dadc423d59fa8df119629b0d4446242a66995
parentscd: New option --pcsc-shared. (diff)
downloadgnupg2-4997838c7b8f56be898e86a9b51f1e7fe5dca6d3.tar.xz
gnupg2-4997838c7b8f56be898e86a9b51f1e7fe5dca6d3.zip
doc: add documentation for gpg's keytotpm command
-- The tpm2d patches introduced a new --edit-key command: keytotpm. Add a descriptive entry explaining what it does and how it works. Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
-rw-r--r--doc/gpg.texi20
1 files changed, 20 insertions, 0 deletions
diff --git a/doc/gpg.texi b/doc/gpg.texi
index 2ba99e5c0..54455b4ac 100644
--- a/doc/gpg.texi
+++ b/doc/gpg.texi
@@ -1002,6 +1002,26 @@ signing.
select 2 to restore as encryption key. You will first be asked to enter
the passphrase of the backup key and then for the Admin PIN of the card.
+ @item keytotpm
+ @opindex keyedit:keytotpm
+ Transfer the selected secret subkey (or the primary key if no subkey
+ has been selected) to TPM form. The secret key in the keyring will
+ be replaced by the TPM representation of that key, which can only be
+ read by the particular TPM that created it (so the keyfile now
+ becomes locked to the laptop containing the TPM). Only certain key
+ types may be transferred to the TPM (all TPM 2.0 systems are
+ mandated to have the rsa2048 and nistp256 algorithms but newer TPMs
+ may have more). Note that the key itself is not transferred into the
+ TPM, merely encrypted by the TPM in-place, so if the keyfile is
+ deleted, the key will be lost. Once transferred to TPM
+ representation, the key file can never be converted back to non-TPM
+ form and the key will die when the TPM does, so you should first
+ have a backup on secure offline storage of the actual secret key
+ file before conversion. It is essential to use the physical system
+ TPM that you have rw permission on the TPM resource manager device
+ (/dev/tpmrm0). Usually this means you must be a member of the tss
+ group.
+
@item delkey
@opindex keyedit:delkey
Remove a subkey (secondary key). Note that it is not possible to retract