From 951657bd0a5bb32b5f56cc6b91ad2ea4094bdfaf Mon Sep 17 00:00:00 2001 From: Harald Hoyer Date: Thu, 11 Apr 2013 15:44:33 +0200 Subject: cryptsetup-generator: add support for rd.luks.key= Also clarify rd.luks.uuid and luks.uuid in the manual. https://bugzilla.redhat.com/show_bug.cgi?id=905683 --- man/systemd-cryptsetup-generator.xml | 26 +++++++++++++++++++++++++- 1 file changed, 25 insertions(+), 1 deletion(-) (limited to 'man/systemd-cryptsetup-generator.xml') diff --git a/man/systemd-cryptsetup-generator.xml b/man/systemd-cryptsetup-generator.xml index 292e967bea..7950032941 100644 --- a/man/systemd-cryptsetup-generator.xml +++ b/man/systemd-cryptsetup-generator.xml @@ -128,7 +128,31 @@ (initrd) while luks.uuid= is honored by both the main system and - the initrd. + the initrd. + If /etc/crypttab contains entries with + the same UUID, then the options for this entry + will be used. + If /etc/crypttab exists, only those UUID + specified on the kernel command line + will be activated in the initrd or the real root. + + + + luks.key= + rd.luks.key= + + Takes a password file as argument. + For those entries specified with + rd.luks.uuid= or luks.uuid=, + the password file will be set to the password file specified by + rd.luks.key= or luks.key + rd.luks.key= + is honored only by initial RAM disk + (initrd) while + luks.key= is + honored by both the main system and + the initrd. + -- cgit v1.2.3