summaryrefslogtreecommitdiff
path: root/man/systemd-cryptenroll.xml
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-12-12 17:44:45 +0100
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-12-13 09:25:31 +0100
commita587a16af290b9abf3bdceffc1679e1de945df4f (patch)
tree6e016999933f8b1e46ee63db51f1d96b772b72a1 /man/systemd-cryptenroll.xml
parent2e081f18d6e3fa7452b76898ad815f8b6e7c1a28 (diff)
downloadsystemd-a587a16af290b9abf3bdceffc1679e1de945df4f.tar.gz
man: reorder item
We said that recovery keys are "similar to regular passphrases" before intorducing "regular passphrases".
Diffstat (limited to 'man/systemd-cryptenroll.xml')
-rw-r--r--man/systemd-cryptenroll.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/man/systemd-cryptenroll.xml b/man/systemd-cryptenroll.xml
index 3b140c37cd..d5fdb54cdd 100644
--- a/man/systemd-cryptenroll.xml
+++ b/man/systemd-cryptenroll.xml
@@ -42,14 +42,14 @@
<listitem><para>TPM2 security devices</para></listitem>
+ <listitem><para>Regular passphrases</para></listitem>
+
<listitem><para>Recovery keys. These are similar to regular passphrases, however are randomly generated
on the computer and thus generally have higher entropy than user-chosen passphrases. Their character
set has been designed to ensure they are easy to type in, while having high entropy. They may also be
scanned off screen using QR codes. Recovery keys may be used for unlocking LUKS2 volumes wherever
passphrases are accepted. They are intended to be used in combination with an enrolled hardware
security token, as a recovery option when the token is lost.</para></listitem>
-
- <listitem><para>Regular passphrases</para></listitem>
</orderedlist>
<para>In addition, the tool may be used to enumerate currently enrolled security tokens and wipe a subset