diff options
author | James O'Beirne <james.obeirne@pm.me> | 2021-03-25 11:37:43 -0400 |
---|---|---|
committer | James O'Beirne <james.obeirne@pm.me> | 2021-03-25 11:40:22 -0400 |
commit | 47cd08551856a4353a6732c165d1c493b3d9f2ad (patch) | |
tree | ae5bedf67225495a6ce616ed47d2bf1789659e4d | |
parent | Merge pull request #218 from DevSecNinja/devsecninja/addPowerShellCommand (diff) | |
download | YubiKey-Guide-47cd08551856a4353a6732c165d1c493b3d9f2ad.tar.gz |
Add note about pass insert error and `trust-key` usage
When using a previously provisioned YubiKey on a new computer,
I was met with an "Unusable public key" error when trying to insert
a new password, despite being able to decrypt pass entries.
I tried setting the trust on the key via `gpg --edit-key`, but was
then met with "Need secret key to do this."
I found that the solution is apparently to use the `trust-key`
directive in `~/.gnupg/gpg.conf`, which is not mentioned in the README
at the moment.
-rw-r--r-- | README.md | 11 |
1 files changed, 11 insertions, 0 deletions
@@ -2480,6 +2480,17 @@ Admin PIN: 12345678 - If you receive the error, `Please insert the card with serial number: *` see [using of multiple keys](#using-multiple-keys). - If you receive the error, `There is no assurance this key belongs to the named user` or `encryption failed: Unusable public key` use `gpg --edit-key` to set `trust` to `5 = I trust ultimately`. + - If, when you try the above `--edit-key` command, you get the error + `Need the secret key to do this.`, you can manually specify trust for the key in + `~/.gnupg/gpg.conf` by using the `trust-key [your key ID]` directive. + +- If, when using a previously provisioned YubiKey on a new computer with `pass`, you see the + following error on `pass insert`: + ``` + gpg: 0x0000000000000000: There is no assurance this key belongs to the named user + gpg: [stdin]: encryption failed: Unusable public key + ``` + 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. |