change defaults and add info to #Require touch
As mentioned in #197, the previous behaviour would require users to touch their key any time an authentication, signing, or encryption operation was performed. In some situations, this behaviour would be undesirable and the only way to revert it would be fully resetting the key and starting from scratch. Rather than using `fixed`, this commit simply turns the feature `on` so the user can change it later if they wish. Additionally, a note about the other policies was included so users can decide for themselves which fits their situation better.
This commit is contained in:
parent
697a7d8fb9
commit
0e7dabeeeb
38
README.md
38
README.md
|
@ -2285,21 +2285,53 @@ To require a touch for each key operation, install [YubiKey Manager](https://dev
|
||||||
Authentication:
|
Authentication:
|
||||||
|
|
||||||
```console
|
```console
|
||||||
$ ykman openpgp set-touch aut fixed
|
$ ykman openpgp set-touch aut on
|
||||||
```
|
```
|
||||||
|
|
||||||
Signing:
|
Signing:
|
||||||
|
|
||||||
```console
|
```console
|
||||||
$ ykman openpgp set-touch sig fixed
|
$ ykman openpgp set-touch sig on
|
||||||
```
|
```
|
||||||
|
|
||||||
Encryption:
|
Encryption:
|
||||||
|
|
||||||
```console
|
```console
|
||||||
$ ykman openpgp set-touch enc fixed
|
$ ykman openpgp set-touch enc on
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Depending on how the YubiKey is going to be used, you may want to look at the policy options for each of these and adjust the above commands accordingly. They can be viewed with the following command:
|
||||||
|
|
||||||
|
```
|
||||||
|
$ ykman openpgp set-touch -h
|
||||||
|
Usage: ykman openpgp set-touch [OPTIONS] KEY POLICY
|
||||||
|
|
||||||
|
Set touch policy for OpenPGP keys.
|
||||||
|
|
||||||
|
KEY Key slot to set (sig, enc, aut or att).
|
||||||
|
POLICY Touch policy to set (on, off, fixed, cached or cached-fixed).
|
||||||
|
|
||||||
|
The touch policy is used to require user interaction for all operations using the private key on the YubiKey. The touch policy is set indivdually for each key slot. To see the current touch policy, run
|
||||||
|
|
||||||
|
$ ykman openpgp info
|
||||||
|
|
||||||
|
Touch policies:
|
||||||
|
|
||||||
|
Off (default) No touch required
|
||||||
|
On Touch required
|
||||||
|
Fixed Touch required, can't be disabled without a full reset
|
||||||
|
Cached Touch required, cached for 15s after use
|
||||||
|
Cached-Fixed Touch required, cached for 15s after use, can't be disabled
|
||||||
|
without a full reset
|
||||||
|
|
||||||
|
Options:
|
||||||
|
-a, --admin-pin TEXT Admin PIN for OpenPGP.
|
||||||
|
-f, --force Confirm the action without prompting.
|
||||||
|
-h, --help Show this message and exit.
|
||||||
|
```
|
||||||
|
|
||||||
|
If the YubiKey is going to be used within an email client that opens and verifies encrypted mail, `Cached` or `Cached-Fixed` may be desirable.
|
||||||
|
|
||||||
YubiKey will blink when it is waiting for a touch. On Linux you can also use [yubikey-touch-detector](https://github.com/maximbaz/yubikey-touch-detector) to have an indicator or notification that YubiKey is waiting for a touch.
|
YubiKey will blink when it is waiting for a touch. On Linux you can also use [yubikey-touch-detector](https://github.com/maximbaz/yubikey-touch-detector) to have an indicator or notification that YubiKey is waiting for a touch.
|
||||||
|
|
||||||
# Email
|
# Email
|
||||||
|
|
Loading…
Reference in New Issue