table of contents
CRYPTSETUP-LUKSHEADERRESTORE(8) | Maintenance Commands | CRYPTSETUP-LUKSHEADERRESTORE(8) |
NAME¶
cryptsetup-luksHeaderRestore - restore a binary backup of the LUKS header and keyslot area
SYNOPSIS¶
cryptsetup luksHeaderRestore --header-backup-file <file> [<options>] <device>
DESCRIPTION¶
Restores a binary backup of the LUKS header and keyslot area from
the specified file.
NOTE: Using '-' as filename reads the header backup from a file named
'-'.
<options> can be [--header, --header-backup-file, --disable-locks].
WARNING: Header and keyslots will be replaced, only the passphrases from the backup will work afterward.
This command requires that the volume key size and data offset of the LUKS header already on the device and of the header backup match. Alternatively, if there is no LUKS header on the device, the backup will also be written to it.
OPTIONS¶
--header <device or file storing the LUKS header>
For commands that change the LUKS header (e.g. luksAddKey), specify the device or file with the LUKS header directly as the LUKS device.
--header-backup-file <file>
--disable-locks
WARNING: Do not use this option unless you run cryptsetup in a restricted environment where locking is impossible to perform (where /run directory cannot be used).
--batch-mode, -q
If the --verify-passphrase option is not specified, this option also switches off the passphrase verification.
--debug or --debug-json
If --debug-json is used, additional LUKS2 JSON data structures are printed.
--version, -V
--usage
--help, -?
Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or in Issues project section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
Please attach output of the failed command with --debug option added.
SEE ALSO¶
Cryptsetup FAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
CRYPTSETUP¶
Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
2023-06-30 | cryptsetup 2.6.0 |