diff options
| author | Jean-Paul van Ravensberg <14926452+DevSecNinja@users.noreply.github.com> | 2021-11-07 13:07:01 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-11-07 13:07:01 +0100 |
| commit | 1a955f88aaf5c02e6588d35d653abc2ee754a984 (patch) | |
| tree | bb925c2555be0331264dda8189282d1339bfb330 | |
| parent | Merge pull request #291 from gaffneyd4/improve-recovery-guide (diff) | |
| download | YubiKey-Guide-1a955f88aaf5c02e6588d35d653abc2ee754a984.tar.gz | |
Add small adjustments after renewing my subkeys
| -rw-r--r-- | README.md | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -1811,7 +1811,7 @@ Enter passphrase for /dev/mmcblk0p1: $ sudo mount /dev/mapper/secret /mnt/encrypted-storage ``` -Import the master key and configuration to a temporary working directory: +Import the master key and configuration to a temporary working directory. Note that Windows users should import mastersub.gpg: ```console $ export GNUPGHOME=$(mktemp -d -t gnupg_$(date +%Y%m%d%H%M)_XXX) @@ -2741,7 +2741,7 @@ Before you unmount your backup, ask yourself if you should make another one just ``` you need to adjust the trust associated with the key. See the above bullet. -- If you receive the error, `gpg: 0x0000000000000000: skipped: Unusable public key` or `encryption failed: Unusable public key` the sub-key may be expired and can no longer be used to encrypt nor sign messages. It can still be used to decrypt and authenticate, however. +- If you receive the error, `gpg: 0x0000000000000000: skipped: Unusable public key`, `signing failed: Unusable secret key`, or `encryption failed: Unusable public key` the sub-key may be expired and can no longer be used to encrypt nor sign messages. It can still be used to decrypt and authenticate, however. - Refer to Yubico article [Troubleshooting Issues with GPG](https://support.yubico.com/hc/en-us/articles/360013714479-Troubleshooting-Issues-with-GPG) for additional guidance. |