1CRYPTSETUP-LUKSHEADERBACKUP(8)Maintenance CommandsCRYPTSETUP-LUKSHEADERBACKUP(8)
2
3
4

NAME

6       cryptsetup-luksHeaderBackup - store a binary backup of the LUKS header
7       and keyslot area
8

SYNOPSIS

10       cryptsetup luksHeaderBackup --header-backup-file <file> [<options>]
11       <device>
12

DESCRIPTION

14       Stores a binary backup of the LUKS header and keyslot area.
15       NOTE: Using '-' as filename writes the header backup to a file named
16       '-'.
17
18       <options> can be [--header, --header-backup-file, --disable-locks].
19
20       WARNING: This backup file and a passphrase valid at the time of backup
21       allows decryption of the LUKS data area, even if the passphrase was
22       later changed or removed from the LUKS device. Also note that with a
23       header backup you lose the ability to securely wipe the LUKS device by
24       just overwriting the header and key-slots. You either need to securely
25       erase all header backups in addition or overwrite the encrypted data
26       area as well. The second option is less secure, as some sectors can
27       survive, e.g., due to defect management.
28

OPTIONS

30       --header <device or file storing the LUKS header>
31           Use a detached (separated) metadata device or file where the LUKS
32           header is stored. This option allows one to store ciphertext and
33           LUKS header on different devices.
34
35           For commands that change the LUKS header (e.g. luksAddKey), specify
36           the device or file with the LUKS header directly as the LUKS
37           device.
38
39       --header-backup-file <file>
40           Specify file with header backup file.
41
42       --disable-locks
43           Disable lock protection for metadata on disk. This option is valid
44           only for LUKS2 and ignored for other formats.
45
46           WARNING: Do not use this option unless you run cryptsetup in a
47           restricted environment where locking is impossible to perform
48           (where /run directory cannot be used).
49
50       --batch-mode, -q
51           Suppresses all confirmation questions. Use with care!
52
53           If the --verify-passphrase option is not specified, this option
54           also switches off the passphrase verification.
55
56       --debug or --debug-json
57           Run in debug mode with full diagnostic logs. Debug output lines are
58           always prefixed by #.
59
60           If --debug-json is used, additional LUKS2 JSON data structures are
61           printed.
62
63       --version, -V
64           Show the program version.
65
66       --usage
67           Show short option help.
68
69       --help, -?
70           Show help text and default parameters.
71

REPORTING BUGS

73       Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or
74       in Issues project section
75       <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
76
77       Please attach output of the failed command with --debug option added.
78

SEE ALSO

80       Cryptsetup FAQ
81       <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
82
83       cryptsetup(8), integritysetup(8) and veritysetup(8)
84

CRYPTSETUP

86       Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
87
88
89
90cryptsetup 2.6.1                  2023-02-10    CRYPTSETUP-LUKSHEADERBACKUP(8)
Impressum