table of contents
CRYPTSETUP-LUKSSUSPEND(8) | Maintenance Commands | CRYPTSETUP-LUKSSUSPEND(8) |
NAME¶
cryptsetup-luksSuspend - suspends an active device and wipes the key
SYNOPSIS¶
cryptsetup luksSuspend [<options>] <name>
DESCRIPTION¶
Suspends an active device (all IO operations will block and accesses to the device will wait indefinitely) and wipes the encryption key from kernel memory. Needs kernel 2.6.19 or later.
After this operation, you have to use luksResume to reinstate the encryption key and unblock the device or close to remove the mapped device.
<options> can be [--header, --disable-locks].
WARNING: Never suspend the device on which the cryptsetup binary resides.
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.
--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 |