From: Zbigniew Jędrzejewski-Szmek Date: Sat, 23 Sep 2023 11:43:55 +0000 (+0200) Subject: man: rename systemd-cryptsetup@.service → systemd-cryptsetup X-Git-Tag: v255-rc1~415^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F29296%2Fhead;p=thirdparty%2Fsystemd.git man: rename systemd-cryptsetup@.service → systemd-cryptsetup We already had the other name as alias, so this just changes what is the "main" name. The text is adjusted to describe the command briefly. --- diff --git a/man/rules/meson.build b/man/rules/meson.build index 2884cc32b41..7e145ac0b17 100644 --- a/man/rules/meson.build +++ b/man/rules/meson.build @@ -914,9 +914,9 @@ manpages = [ ['systemd-creds', '1', [], ''], ['systemd-cryptenroll', '1', [], 'HAVE_LIBCRYPTSETUP'], ['systemd-cryptsetup-generator', '8', [], 'HAVE_LIBCRYPTSETUP'], - ['systemd-cryptsetup@.service', + ['systemd-cryptsetup', '8', - ['systemd-cryptsetup'], + ['systemd-cryptsetup@.service'], 'HAVE_LIBCRYPTSETUP'], ['systemd-debug-generator', '8', [], ''], ['systemd-delta', '1', [], ''], diff --git a/man/systemd-cryptsetup@.service.xml b/man/systemd-cryptsetup.xml similarity index 69% rename from man/systemd-cryptsetup@.service.xml rename to man/systemd-cryptsetup.xml index 91a4f2eb9d8..493236da83d 100644 --- a/man/systemd-cryptsetup@.service.xml +++ b/man/systemd-cryptsetup.xml @@ -3,38 +3,62 @@ - + - systemd-cryptsetup@.service + systemd-cryptsetup systemd - systemd-cryptsetup@.service + systemd-cryptsetup 8 + systemd-cryptsetup systemd-cryptsetup@.service - systemd-cryptsetup Full disk decryption logic + + systemd-cryptsetup + OPTIONS + attach + VOLUME + SOURCE-DEVICE + KEY-FILE + CONFIG + + + + systemd-cryptsetup + OPTIONS + detach + VOLUME + + systemd-cryptsetup@.service system-systemd\x2dcryptsetup.slice - systemd-cryptsetup Description - systemd-cryptsetup@.service is a service responsible for setting up encrypted - block devices. It is instantiated for each device that requires decryption for access. + systemd-cryptsetup is used to set up (with attach) and tear + down (with detach) access to an encrypted block device. It is primarily used via + systemd-cryptsetup@.service during early boot, but may also be be called manually. + The positional arguments VOLUME, SOURCEDEVICE, + KEY-FILE, and CRYPTTAB-OPTIONS have the same meaning as the + fields in crypttab5. + + + systemd-cryptsetup@.service is a service responsible for providing access to + encrypted block devices. It is instantiated for each device that requires decryption. systemd-cryptsetup@.service instances are part of the system-systemd\x2dcryptsetup.slice slice, which is destroyed only very late in the @@ -51,9 +75,9 @@ translated into systemd-cryptsetup@.service units by systemd-cryptsetup-generator8. - In order to unlock a volume a password or binary key is - required. systemd-cryptsetup@.service tries to acquire a suitable password or binary - key via the following mechanisms, tried in order: + In order to unlock a volume a password or binary key is required. + systemd-cryptsetup@.service tries to acquire a suitable password or binary key via + the following mechanisms, tried in order: If a key file is explicitly configured (via the third column in @@ -67,8 +91,8 @@ too, if a PKCS#11/FIDO2/TPM2 token/device is configured, any key found this way is decrypted before use. - If the try-empty-password option is specified it is then attempted - to unlock the volume with an empty password. + If the try-empty-password option is specified then unlocking the + volume with an empty password is attempted. The kernel keyring is then checked for a suitable cached password from previous attempts.