<\/a> <\/h2>\nsystemd\u2212cryptsetup\u2212generator understands the following kernel command line parameters:<\/p>\n
luks=<\/i>, rd.luks=<\/i><\/p>\n
Takes a boolean argument. Defaults to “yes”. If “no”, disables the generator entirely. rd.luks=<\/i> is honored only by initial RAM disk (initrd) while luks=<\/i> is honored by both the main system and the initrd.<\/p>\n
luks.crypttab=<\/i>, rd.luks.crypttab=<\/i><\/p>\n
Takes a boolean argument. Defaults to “yes”. If “no”, causes the generator to ignore any devices configured in \/etc\/crypttab (luks.uuid=<\/i> will still work however). rd.luks.crypttab=<\/i> is honored only by initial RAM disk (initrd) while luks.crypttab=<\/i> is honored by both the main system and the initrd.<\/p>\n
luks.uuid=<\/i>, rd.luks.uuid=<\/i><\/p>\n
Takes a LUKS superblock UUID as argument. This will activate the specified device as part of the boot process as if it was listed in \/etc\/crypttab. This option may be specified more than once in order to set up multiple devices. rd.luks.uuid=<\/i> is honored only by initial RAM disk (initrd) while luks.uuid=<\/i> is honored by both the main system and the initrd.<\/p>\n
If \/etc\/crypttab contains entries with the same UUID, then the name, keyfile and options specified there will be used. Otherwise, the device will have the name “luks\u2212UUID”.<\/p>\n
If \/etc\/crypttab exists, only those UUIDs specified on the kernel command line will be activated in the initrd or the real root.<\/p>\n
luks.name=<\/i>, rd.luks.name=<\/i><\/p>\n
Takes a LUKS super block UUID followed by an “=” and a name. This implies rd.luks.uuid=<\/i> or luks.uuid=<\/i> and will additionally make the LUKS device given by the UUID appear under the provided name.<\/p>\n
rd.luks.name=<\/i> is honored only by initial RAM disk (initrd) while luks.name=<\/i> is honored by both the main system and the initrd.<\/p>\n
luks.options=<\/i>, rd.luks.options=<\/i><\/p>\n
Takes a LUKS super block UUID followed by an “=” and a string of options separated by commas as argument. This will override the options for the given UUID.<\/p>\n
If only a list of options, without an UUID, is specified, they apply to any UUIDs not specified elsewhere, and without an entry in \/etc\/crypttab.<\/p>\n
rd.luks.options=<\/i> is honored only by initial RAM disk (initrd) while luks.options=<\/i> is honored by both the main system and the initrd.<\/p>\n
luks.key=<\/i>, rd.luks.key=<\/i><\/p>\n
Takes a password file name as argument or a LUKS super block UUID followed by a “=” and a password file name.<\/p>\n
For those entries specified with rd.luks.uuid=<\/i> or luks.uuid=<\/i>, the password file will be set to the one specified by rd.luks.key=<\/i> or luks.key=<\/i> of the corresponding UUID, or the password file that was specified without a UUID.<\/p>\n
It is also possible to specify an external device which should be mounted before we attempt to unlock the LUKS device. systemd\u2212cryptsetup will use password file stored on that device. Device containing password file is specified by appending colon and a device identifier to the password file path. For example, rd.luks.uuid=<\/i>b40f1abf\u22122a53\u2212400a\u2212889a\u22122eccc27eaa40 rd.luks.key=<\/i>b40f1abf\u22122a53\u2212400a\u2212889a\u22122eccc27eaa40=\/keyfile:LABEL=keydev. Hence, in this case, we will attempt to mount file system residing on the block device with label “keydev”. This syntax is for now only supported on a per\u2212device basis, i.e. you have to specify LUKS device UUID.<\/p>\n
rd.luks.key=<\/i> is honored only by initial RAM disk (initrd) while luks.key=<\/i> is honored by both the main system and the initrd.<\/p>\n