NAME
cryptsetup-luksDump - dump the header information of a LUKS deviceSYNOPSIS
cryptsetup luksDump [<options>] <device>DESCRIPTION
Dump the header information of a LUKS device.OPTIONS
--type <device-type>Specifies required device type, for more info
read BASIC ACTIONS section in cryptsetup(8).
Read the passphrase from 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.
Skip value bytes at the beginning of
the key file.
Read a maximum of value bytes from the
key file. The default is to read the whole file up to the compiled-in maximum
that can be queried with --help. Supplying more data than the compiled-in
maximum aborts the operation.
This option is useful to cut trailing newlines, for example. If --keyfile-offset
is also given, the size count starts after the offset.
Use a volume key stored in a file. The volume
key is stored in a file instead of being printed out to standard output.
For luksDump (LUKS2 only) this option
prints content of LUKS2 header JSON metadata area.
Print the volume key in the displayed
information. Use with care, as the volume key can be used to bypass the
passphrases, see also option --volume-key-file.
For LUKS operations that add key material,
this option allows you to specify which key slot is selected for the new key.
The maximum number of key slots depends on the LUKS version. LUKS1 can have up
to 8 key slots. LUKS2 can have up to 32 key slots based on key slot area size
and key size, but a valid key slot ID can always be between 0 and 31 for
LUKS2.
The number of seconds to wait before timeout
on passphrase input via terminal. It is relevant every time a passphrase is
asked. It has no effect if used in conjunction with --key-file.
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.
Use a detached (separated) metadata device or
file where the LUKS header is stored. This option allows one to store
ciphertext and LUKS header on different devices.
For commands that change the LUKS header (e.g. luksAddKey), specify the
device or file with the LUKS header directly as the LUKS device.
Disable lock protection for metadata on disk.
This option is valid only for LUKS2 and ignored for other formats.
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).
Dumps existing LUKS2 unbound keyslot.
Suppresses all confirmation questions. Use
with care!
If the --verify-passphrase option is not specified, this option also switches
off the passphrase verification.
Run in debug mode with full diagnostic logs.
Debug output lines are always prefixed by #.
If --debug-json is used, additional LUKS2 JSON data structures are
printed.
Show the program version.
Show short option help.
Show help text and default parameters.
REPORTING BUGS
Report bugs at cryptsetup <[email protected]>mailing or in Issues project section <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.SEE ALSO
Cryptsetup FAQ <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>CRYPTSETUP
Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.2023-12-18 | cryptsetup 2.6.1 |