CRYPTSETUP-BITLKDUMP(8) | Maintenance Commands | CRYPTSETUP-BITLKDUMP(8) |
NAME
cryptsetup-bitlkDump - dump the header information of a BITLK (BitLocker compatible) device
SYNOPSIS
cryptsetup bitlkDump [<options>] <device>
DESCRIPTION
Dump the header information of a BITLK (BitLocker compatible) device.
If the --dump-volume-key option is used, the BITLK device volume key is dumped instead of header information. You have to provide a password or keyfile to dump the volume key.
Beware that the volume key can be used to decrypt the data stored in the container without a passphrase. This means that if the volume key is compromised, the whole device has to be erased to prevent further access. Use this option carefully.
<options> can be [--dump-volume-key, --volume-key-file, --key-file, --keyfile-offset, --keyfile-size, --timeout].
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.
--dump-volume-key, --dump-master-key (OBSOLETE alias)
--help, -?
--key-file, -d file
If the name given is "-", then the passphrase will be read from stdin. In this case, reading will not stop at newline characters.
See section NOTES ON PASSPHRASE PROCESSING in cryptsetup(8) for more information.
--keyfile-offset value
--keyfile-size, -l value
This option is useful to cut trailing newlines, for example. If --keyfile-offset is also given, the size count starts after the offset.
--timeout, -t seconds
This option is useful when the system should not stall if the user does not input a passphrase, e.g., during boot. The default is a value of 0 seconds, which means to wait forever.
--usage
--version, -V
--volume-key-file file, --master-key-file file (OBSOLETE alias)
The volume key is stored in a file instead of being printed out to standard output.
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/.
2025-08-13 | cryptsetup 2.8.1 |