diff options
Diffstat (limited to 'man/systemd-cryptenroll.xml')
| -rw-r--r-- | man/systemd-cryptenroll.xml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/man/systemd-cryptenroll.xml b/man/systemd-cryptenroll.xml index fb36f455ba..949e07fd63 100644 --- a/man/systemd-cryptenroll.xml +++ b/man/systemd-cryptenroll.xml @@ -229,7 +229,7 @@ <para>Note that currently when enrolling a new key of one of the five supported types listed above, it is required to first provide a passphrase, a recovery key, a FIDO2 token, or a TPM2 key. It's currently not supported to unlock a device with a PKCS#11 key in order to enroll a new PKCS#11 key. Thus, if in future - key roll-over is desired it's generally recommended to ensure a passphrase, a recovery key, a FIDO2 + key roll-over is desired it is generally recommended to ensure a passphrase, a recovery key, a FIDO2 token, or a TPM2 key is always enrolled.</para> <para>Also note that support for enrolling multiple FIDO2 tokens is currently limited. When multiple FIDO2 @@ -398,7 +398,7 @@ is unsupported if <option>--unlock-fido2-device=</option> option is also specified. The special value <literal>list</literal> may be used to enumerate all suitable FIDO2 tokens currently plugged in. Note that many hardware security tokens that implement FIDO2 also implement the older PKCS#11 - standard. Typically FIDO2 is preferable, given it's simpler to use and more modern.</para> + standard. Typically FIDO2 is preferable, given it is simpler to use and more modern.</para> <para>In order to unlock a LUKS2 volume with an enrolled FIDO2 security token, specify the <option>fido2-device=</option> option in the respective <filename>/etc/crypttab</filename> line:</para> |