diff options
| author | Sebastian Schmieschek <sebastian@schmie.net> | 2020-05-27 10:30:09 +0100 |
|---|---|---|
| committer | Sebastian Schmieschek <sebastian@schmie.net> | 2020-05-27 11:46:19 +0100 |
| commit | e1055025feda0568ccf2f59ad675fd0b8edd6d85 (patch) | |
| tree | 404b285d6a42a75cc633e37abf3291802f24205b /README.md | |
| parent | Stack rank secure environment and add a few tips (diff) | |
| download | YubiKey-Guide-e1055025feda0568ccf2f59ad675fd0b8edd6d85.tar.gz | |
Add information on potential PIN issues and how to debug them
I missed the error message when attempting to set a PIN of only 5 characters due
to the UI repeating the options below it.
Pinentry happily stores the bogus PIN and even counts down the retry counter
when entering the correct (default) one. This can be resolved by unblocking the
PIN.
Once I ran the gpg-agent with debug output (a tip found in the added link), the
issue was obvious.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -1246,7 +1246,7 @@ Use the [YubiKey Manager](https://developers.yubico.com/yubikey-manager) applica ## Change PIN -The default PIN is `123456` and default Admin PIN (PUK) is `12345678`. CCID-mode PINs can be up to 127 ASCII characters. +The default PIN is `123456` and default Admin PIN (PUK) is `12345678`. CCID-mode PINs can be up to 127 ASCII characters. They have to be at least 6 (PIN) or 8 (PUK) ASCII characters. The Admin PIN is required for some card operations and to unblock a PIN that has been entered incorrectly more than three times. See the GnuPG documentation on [Managing PINs](https://www.gnupg.org/howtos/card-howto/en/ch03s02.html) for details. @@ -2357,9 +2357,11 @@ Admin PIN: 12345678 - Use `man gpg` to understand GPG options and command-line flags. +- To get more information on potential errors, restart the `gpg-agent` process with debug output to the console with `pkill gpg-agent; gpg-agent --daemon --no-detach -v -v --debug-level advanced --homedir ~/.gnupg`. + - If you encounter problems connecting to YubiKey with GPG - try unplugging and re-inserting YubiKey, and restarting the `gpg-agent` process. -- If you receive the error, `gpg: decryption failed: secret key not available` - you likely need to install GnuPG version 2.x. +- If you receive the error, `gpg: decryption failed: secret key not available` - you likely need to install GnuPG version 2.x. Another possibility is that there is a problem with the PIN, e.g. it is too short or blocked. - If you receive the error, `Yubikey core error: no yubikey present` - make sure the YubiKey is inserted correctly. It should blink once when plugged in. @@ -2415,3 +2417,4 @@ Admin PIN: 12345678 * https://www.hanselman.com/blog/HowToSetupSignedGitCommitsWithAYubiKeyNEOAndGPGAndKeybaseOnWindows.aspx * https://www.void.gr/kargig/blog/2013/12/02/creating-a-new-gpg-key-with-subkeys/ * https://mlohr.com/gpg-agent-forwarding/ +* https://www.ingby.com/?p=293 |