summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Nemish <anemish@gmail.com>2023-12-15 11:00:10 +0100
committerGitHub <noreply@github.com>2023-12-15 11:00:10 +0100
commitb434f1813ca2d4c270b51e53a4b7acd52f69bf60 (patch)
tree51522608880a17264462658f1265855850e04aba
parent9692c70eadc193d87900225cf3d9728a849568e2 (diff)
downloadbips-b434f1813ca2d4c270b51e53a4b7acd52f69bf60.tar.xz
Update bip-0085.mediawiki
Fix doublicated word
-rw-r--r--bip-0085.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-0085.mediawiki b/bip-0085.mediawiki
index 0627755..d5557fb 100644
--- a/bip-0085.mediawiki
+++ b/bip-0085.mediawiki
@@ -364,7 +364,7 @@ The resulting RSA key can be used to create a GPG key where the creation date MU
Note on GPG key capabilities on smartcard/hardware devices:
-GPG capable smart-cards SHOULD be be loaded as follows: The encryption slot SHOULD be loaded with the ENCRYPTION capable key; the authentication slot SHOULD be loaded with the AUTHENTICATION capable key. The signature capable slot SHOULD be loaded with the SIGNATURE capable key.
+GPG capable smart-cards SHOULD be loaded as follows: The encryption slot SHOULD be loaded with the ENCRYPTION capable key; the authentication slot SHOULD be loaded with the AUTHENTICATION capable key. The signature capable slot SHOULD be loaded with the SIGNATURE capable key.
However, depending on available slots on the smart-card, and preferred policy, the CERTIFY capable key MAY be flagged with CERTIFY and SIGNATURE capabilities and loaded into the SIGNATURE capable slot (for example where the smart-card has only three slots and the CERTIFY capability is required on the same card). In this case, the SIGNATURE capable sub-key would be disregarded because the CERTIFY capable key serves a dual purpose.