cryptsetup-luksHeaderBackup(8)
| CRYPTSETUP-LUKSHEADERBACKUP(8) | Maintenance Commands | CRYPTSETUP-LUKSHEADERBACKUP(8) |
NAME
cryptsetup-luksHeaderBackup - store a binary backup of the LUKS header and keyslot area
SYNOPSIS
cryptsetup luksHeaderBackup --header-backup-file <file> [<options>] <device>
DESCRIPTION
Stores a binary backup of the LUKS header and keyslot area.
Using '-' as a filename writes the header backup to a file named '-'.
The backup file and a passphrase valid at the time of backup allow decryption of the LUKS data area, even if the passphrase was later changed or removed from the LUKS device. Note that with a header backup, you lose the ability to wipe the LUKS device securely by just overwriting the header and keyslots. You must either securely erase all header backups or overwrite the encrypted data area.
<options> can be [--header, --header-backup-file, --disable-locks].
OPTIONS
--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.
--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).
--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
--help, -?
--usage
--version, -V
REPORTING BUGS
Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or in Issues project section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
Please attach the 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/>.
| 2026-02-20 | cryptsetup 2.8.4 |
