diff options
| author | drduh <github@duh.to> | 2022-12-26 11:13:43 -0800 |
|---|---|---|
| committer | drduh <github@duh.to> | 2022-12-26 11:13:43 -0800 |
| commit | ad340b5f18d71b3f227cc1d881ee6a7068778dca (patch) | |
| tree | 5ab14f4aa0944c8cfcf994487b16b057da1fc85b | |
| parent | Note public key recovery article (diff) | |
| download | YubiKey-Guide-ad340b5f18d71b3f227cc1d881ee6a7068778dca.tar.gz | |
mention forcesig flag to prompt pin each time
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -2259,7 +2259,7 @@ max-cache-ttl 120 pinentry-program /usr/bin/pinentry-curses ``` -**Important** The `cache-ttl` options do **NOT** apply when using a YubiKey as a smartcard as the PIN is [cached by the smartcard itself](https://dev.gnupg.org/T3362). Therefore, in order to clear the PIN from cache (smartcard equivalent to `default-cache-ttl` and `max-cache-ttl`), you need to unplug the YubiKey. +**Important** The `cache-ttl` options do **NOT** apply when using a YubiKey as a smartcard as the PIN is [cached by the smartcard itself](https://dev.gnupg.org/T3362). Therefore, in order to clear the PIN from cache (smartcard equivalent to `default-cache-ttl` and `max-cache-ttl`), you need to unplug the YubiKey, or set the `forcesig` flag when editing the card to be prompted for the PIN each time. **Tip** Set `pinentry-program /usr/bin/pinentry-gnome3` for a GUI-based prompt. If the _pinentry_ graphical dialog doesn't show and you get this error: `sign_and_send_pubkey: signing failed: agent refused operation`, you may need to install the `dbus-user-session` package and restart the computer for the `dbus` user session to be fully inherited; this is because behind the scenes, `pinentry` complains about `No $DBUS_SESSION_BUS_ADDRESS found`, falls back to `curses` but doesn't find the expected `tty`. |