mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 00:14:32 +09:00
man: replace "-" with "none" in cryptsetup commands and crypttab
`none` is more explicit and harder to overlook than `-` which in certain contexts could be misunderstood to mean standard input.
This commit is contained in:
@@ -5,7 +5,7 @@
|
||||
sudo systemd-cryptenroll --fido2-device=auto /dev/sdXn
|
||||
|
||||
# Test: Let's run systemd-cryptsetup to test if this worked.
|
||||
sudo systemd-cryptsetup attach mytest /dev/sdXn - fido2-device=auto
|
||||
sudo systemd-cryptsetup attach mytest /dev/sdXn none fido2-device=auto
|
||||
|
||||
# If that worked, let's now add the same line persistently to /etc/crypttab,
|
||||
# for the future. We do not want to use the (unstable) /dev/sdX name, so let's
|
||||
@@ -13,7 +13,7 @@ sudo systemd-cryptsetup attach mytest /dev/sdXn - fido2-device=auto
|
||||
udevadm info -q symlink -r /dev/sdXn
|
||||
|
||||
# Now add the line using the by-uuid symlink to /etc/crypttab:
|
||||
sudo bash -c 'echo "mytest /dev/disk/by-uuid/... - fido2-device=auto" >>/etc/crypttab'
|
||||
sudo bash -c 'echo "mytest /dev/disk/by-uuid/... none fido2-device=auto" >>/etc/crypttab'
|
||||
|
||||
# Depending on your distribution and encryption setup, you may need to manually
|
||||
# regenerate your initramfs to be able to use a FIDO2 device to unlock the
|
||||
|
||||
@@ -369,7 +369,7 @@
|
||||
<para>In order to unlock a LUKS2 volume with an enrolled PKCS#11 security token, specify the
|
||||
<option>pkcs11-uri=</option> option in the respective <filename>/etc/crypttab</filename> line:</para>
|
||||
|
||||
<programlisting>myvolume /dev/sda1 - pkcs11-uri=auto</programlisting>
|
||||
<programlisting>myvolume /dev/sda1 none pkcs11-uri=auto</programlisting>
|
||||
|
||||
<para>See
|
||||
<citerefentry><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a
|
||||
@@ -403,7 +403,7 @@
|
||||
<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>
|
||||
|
||||
<programlisting>myvolume /dev/sda1 - fido2-device=auto</programlisting>
|
||||
<programlisting>myvolume /dev/sda1 none fido2-device=auto</programlisting>
|
||||
|
||||
<para>See
|
||||
<citerefentry><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a
|
||||
@@ -507,7 +507,7 @@
|
||||
<para>In order to unlock a LUKS2 volume with an enrolled TPM2 security chip, specify the
|
||||
<option>tpm2-device=</option> option in the respective <filename>/etc/crypttab</filename> line:</para>
|
||||
|
||||
<programlisting>myvolume /dev/sda1 - tpm2-device=auto</programlisting>
|
||||
<programlisting>myvolume /dev/sda1 none tpm2-device=auto</programlisting>
|
||||
|
||||
<para>See
|
||||
<citerefentry><refentrytitle>crypttab</refentrytitle><manvolnum>5</manvolnum></citerefentry> for a
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
sudo systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sdXn
|
||||
|
||||
# Test: Let's run systemd-cryptsetup to test if this worked.
|
||||
sudo systemd-cryptsetup attach mytest /dev/sdXn - tpm2-device=auto
|
||||
sudo systemd-cryptsetup attach mytest /dev/sdXn none tpm2-device=auto
|
||||
|
||||
# If that worked, let's now add the same line persistently to /etc/crypttab,
|
||||
# for the future. We do not want to use the (unstable) /dev/sdX name, so let's
|
||||
@@ -13,7 +13,7 @@ sudo systemd-cryptsetup attach mytest /dev/sdXn - tpm2-device=auto
|
||||
udevadm info -q symlink -r /dev/sdXn
|
||||
|
||||
# Now add the line using the by-uuid symlink to /etc/crypttab:
|
||||
sudo bash -c 'echo "mytest /dev/disk/by-uuid/... - tpm2-device=auto" >>/etc/crypttab'
|
||||
sudo bash -c 'echo "mytest /dev/disk/by-uuid/... none tpm2-device=auto" >>/etc/crypttab'
|
||||
|
||||
# And now let's check that automatic unlocking works:
|
||||
sudo systemd-cryptsetup detach mytest
|
||||
|
||||
@@ -21,7 +21,7 @@ rm pubkey.pem
|
||||
sudo systemd-cryptenroll --pkcs11-token-uri=auto /dev/sdXn
|
||||
|
||||
# Test: Let's run systemd-cryptsetup to test if this all worked.
|
||||
sudo systemd-cryptsetup attach mytest /dev/sdXn - pkcs11-uri=auto
|
||||
sudo systemd-cryptsetup attach mytest /dev/sdXn none pkcs11-uri=auto
|
||||
|
||||
# If that worked, let's now add the same line persistently to /etc/crypttab,
|
||||
# for the future. We do not want to use the (unstable) /dev/sdX name, so let's
|
||||
@@ -29,7 +29,7 @@ sudo systemd-cryptsetup attach mytest /dev/sdXn - pkcs11-uri=auto
|
||||
udevadm info -q symlink -r /dev/sdXn
|
||||
|
||||
# Now add the line using the by-uuid symlink to /etc/crypttab:
|
||||
sudo bash -c 'echo "mytest /dev/disk/by-uuid/... - pkcs11-uri=auto" >>/etc/crypttab'
|
||||
sudo bash -c 'echo "mytest /dev/disk/by-uuid/... none pkcs11-uri=auto" >>/etc/crypttab'
|
||||
|
||||
# Depending on your distribution and encryption setup, you may need to manually
|
||||
# regenerate your initramfs to be able to use a Yubikey / PKCS#11 token to
|
||||
|
||||
Reference in New Issue
Block a user