Changes
Page history
improve documentation on "No YubiKey found" errors
authored
Sep 10, 2024
by
anarcat
Show whitespace changes
Inline
Side-by-side
howto/yubikey.md
View page @
e1a9f2ff
...
@@ -38,8 +38,8 @@ The decision on USB-C vs USB-A should be relatively simple:
...
@@ -38,8 +38,8 @@ The decision on USB-C vs USB-A should be relatively simple:
2.
if you want to go USB-C only, use USB-C, but be aware there's been
2.
if you want to go USB-C only, use USB-C, but be aware there's been
anecdotal reports of the USB-C form factor being more fragile than
anecdotal reports of the USB-C form factor being more fragile than
the USB-A form
(
the connector can apparently get dented, although
the USB-A form
.
the connector can apparently get dented, although
other reports claim this has been fixed
)
other reports claim this has been fixed
.
The decision between "normal" and "nano" depends mostly on how big you
The decision between "normal" and "nano" depends mostly on how big you
like the key, but also how sturdy you expect it to be.
like the key, but also how sturdy you expect it to be.
...
@@ -1111,6 +1111,18 @@ options: either disable sending the `<Enter>` character using `ykman otp
...
@@ -1111,6 +1111,18 @@ options: either disable sending the `<Enter>` character using `ykman otp
settings --no-enter 1`
, or swap the OTP to slot 2, which requires a sustained
settings --no-enter 1`
, or swap the OTP to slot 2, which requires a sustained
2-second touch to activate, with
`ykman otp swap`
.
2-second touch to activate, with
`ykman otp swap`
.
### I'm getting a "No YubiKey found" error
When running the
`ykman`
command, you might stumble upon the following error:
Error: No YubiKey found with the given interface(s)
This might happen because GnuPG (or probably a lock contention between
`ykman`
's
`pcscd`
and GnuPG's
`scdaemon`
).
The fix is unclear, but a workaround is to disconnect and reconnect
your YubiKey.
## Pager playbook
## Pager playbook
<!-- information about common errors from the monitoring system and -->
<!-- information about common errors from the monitoring system and -->
...
...
...
...