'\" t
.\"     Title: cryptsetup-luksresume
.\"    Author: [see the "AUTHOR(S)" section]
.\" Generator: Asciidoctor 2.0.20
.\"      Date: 2025-08-20
.\"    Manual: Maintenance Commands
.\"    Source: cryptsetup 2.8.1
.\"  Language: English
.\"
.TH "CRYPTSETUP\-LUKSRESUME" "8" "2025-08-20" "cryptsetup 2.8.1" "Maintenance Commands"
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.ss \n[.ss] 0
.nh
.ad l
.de URL
\fI\\$2\fP <\\$1>\\$3
..
.als MTO URL
.if \n[.g] \{\
.  mso www.tmac
.  am URL
.    ad l
.  .
.  am MTO
.    ad l
.  .
.  LINKSTYLE blue R < >
.\}
.SH "NAME"
cryptsetup-luksResume \- resume a suspended device and reinstate the key
.SH "SYNOPSIS"
.sp
\fBcryptsetup \fIluksResume\fP [<options>] <name>\fP
.SH "DESCRIPTION"
.sp
Resumes a suspended device and reinstates the encryption key.
Prompts interactively for a passphrase if no token is usable (LUKS2 only) or \-\-key\-file is not given.
.sp
\fB<options>\fP can be [\-\-key\-file, \-\-keyfile\-size, \-\-keyfile\-offset, \-\-key\-slot, \-\-header, \-\-disable\-keyring, \-\-disable\-locks, \-\-token\-id, \-\-token\-only, \-\-token\-type, \-\-disable\-external\-tokens, \-\-type, \-\-tries, \-\-timeout, \-\-verify\-passphrase, \-\-volume\-key\-keyring, \-\-link\-vk\-to\-keyring, \-\-external\-tokens\-path].
.SH "OPTIONS"
.sp
\fB\-\-batch\-mode\fP, \fB\-q\fP
.RS 4
Suppresses all confirmation questions.
Use with care!
.sp
If the \-\-verify\-passphrase option is not specified, this option also switches off the passphrase verification.
.RE
.sp
\fB\-\-debug\fP or \fB\-\-debug\-json\fP
.RS 4
Run in debug mode with full diagnostic logs.
Debug output lines are always prefixed by \fB#\fP.
.sp
If \-\-debug\-json is used, additional LUKS2 JSON data structures are printed.
.RE
.sp
\fB\-\-disable\-external\-tokens\fP
.RS 4
Disable loading of plugins for external LUKS2 tokens.
.RE
.sp
\fB\-\-disable\-keyring\fP
.RS 4
Do not load the volume key in the kernel keyring; store it directly in the dm\-crypt target instead.
This option is supported only for the LUKS2 type.
.RE
.sp
\fB\-\-disable\-locks\fP
.RS 4
Disable lock protection for metadata on disk.
This option is valid only for LUKS2 and is ignored for other formats.
.sp
\fBWARNING:\fP 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).
.RE
.sp
\fB\-\-external\-tokens\-path\fP \fI<absolute path>\fP
.RS 4
Override the system directory path where cryptsetup searches for external token handlers (or token plugins).
It must be an absolute path (starting with \*(Aq/\*(Aq character).
.RE
.sp
\fB\-\-header\fP \fI<device or file storing the LUKS header>\fP
.RS 4
Use a detached (separated) metadata device or file where the LUKS header is stored.
This option allows one to store the ciphertext and LUKS header on different devices.
.sp
For commands that change the LUKS header (e.g., \fIluksAddKey\fP), specify the device or file with the LUKS header directly as the LUKS device.
.RE
.sp
\fB\-\-help\fP, \fB\-?\fP
.RS 4
Show help text and default parameters.
.RE
.sp
\fB\-\-key\-description\fP \fItext\fP
.RS 4
Set the key description in the keyring that will be used for passphrase retrieval.
.RE
.sp
\fB\-\-key\-file\fP, \fB\-d\fP \fIfile\fP
.RS 4
Read the passphrase from the file.
.sp
If the name given is "\-", then the passphrase will be read from stdin.
In this case, reading will not stop at newline characters.
.sp
See section \fINOTES ON PASSPHRASE PROCESSING\fP in \fBcryptsetup\fP(8) for more information.
.RE
.sp
\fB\-\-keyfile\-offset\fP \fIvalue\fP
.RS 4
Skip \fIvalue\fP bytes at the beginning of the key file.
.RE
.sp
\fB\-\-keyfile\-size\fP, \fB\-l\fP \fIvalue\fP
.RS 4
Read a maximum of \fIvalue\fP 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.
.sp
This option is useful to cut trailing newlines, for example.
If \-\-keyfile\-offset is also given, the size count starts after the offset.
.RE
.sp
\fB\-\-key\-slot\fP, \fB\-S\fP \fI<0\-N>\fP
.RS 4
For LUKS operations that add key material, this option allows you to specify which keyslot is selected for the new key.
.sp
The maximum number of keyslots depends on the LUKS version.
LUKS1 can have up to 8 keyslots.
LUKS2 can have up to 32 keyslots based on keyslot area size and key size, but a valid keyslot ID can always be between 0 and 31 for LUKS2.
.RE
.sp
\fB\-\-link\-vk\-to\-keyring\fP \fI<keyring description>::<key description>\fP
.RS 4
Link the volume key in a keyring with the specified key name.
The volume key is linked only if the requested action is successfully finished (with \-\-test\-passphrase, the verified volume key is linked in a keyring without taking further action).
.sp
The \fI<keyring description>\fP string has to contain the existing kernel keyring description.
The keyring name may be optionally prefixed with "%:" or "%keyring:" type descriptions.
Or, the keyring may also be specified directly by numeric key id.
Also, special keyring notations starting with "@" may be used to select existing predefined kernel keyrings.
.sp
The string "::" is a delimiter used to separate the keyring description and key description.
.sp
\fI<key description>\fP part describes key type and key name of volume key linked in the keyring described in \fI<keyring description>\fP.
The type may be specified by adding a "%<type_name>:" prefix in front of the key name.
If the type is missing, the default \fIuser\fP type is applied.
If the key of the same name and type already exists (already linked in the keyring), it will get replaced in the process.
.sp
See also the \fBKEY IDENTIFIERS\fP section of \fBkeyctl\fP(1).
.RE
.sp
\fB\-\-timeout\fP, \fB\-t\fP \fIseconds\fP
.RS 4
The number of seconds to wait before a 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.
.sp
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.
.RE
.sp
\fB\-\-token\-id\fP
.RS 4
Specify what token to use and allow the token PIN prompt to take precedence over the interactive keyslot passphrase prompt.
If omitted, all available tokens (not protected by PIN) will be checked before proceeding further with the passphrase prompt.
.RE
.sp
\fB\-\-token\-only\fP
.RS 4
Do not proceed further with the action if the token\-based keyslot unlock failed.
Without the option, the action asks for a passphrase to proceed further.
.sp
It allows LUKS2 tokens protected by PIN to take precedence over the interactive keyslot passphrase prompt.
.RE
.sp
\fB\-\-token\-type\fP \fItype\fP
.RS 4
Restrict tokens eligible for operation to a specific token \fItype\fP.
Mostly useful when no \-\-token\-id is specified.
.sp
It allows LUKS2 \fItype\fP tokens protected by PIN to take precedence over the interactive keyslot passphrase prompt.
.RE
.sp
\fB\-\-tries\fP, \fB\-T\fP
.RS 4
How often the input of the passphrase shall be retried.
The default is 3 tries.
.RE
.sp
\fB\-\-type\fP \fItype\fP
.RS 4
Specifies required device type, for more info, read the \fIBASIC ACTIONS\fP section in \fBcryptsetup\fP(8).
.RE
.sp
\fB\-\-usage\fP
.RS 4
Show short option help.
.RE
.sp
\fB\-\-verify\-passphrase\fP, \fB\-y\fP
.RS 4
When interactively asking for a passphrase, ask for it twice and complain if both inputs do not match.
Ignored on input from file or stdin.
.RE
.sp
\fB\-\-version\fP, \fB\-V\fP
.RS 4
Show the program version.
.RE
.sp
\fB\-\-volume\-key\-keyring\fP \fI<key description>\fP
.RS 4
Use a volume key stored in a keyring.
This allows one to open \fIluks\fP and \fIplain\fP device types without giving a passphrase.
.sp
For LUKS, the key and associated type have to be readable from userspace so that the volume key digest may be verified before activation.
For devices in reencryption, the option may be used twice to specify both old and new volume keys.
.sp
For PLAIN type, the user must ensure that the key in the keyring is unchanged since activation.
Otherwise, reloading the key can cause data corruption after an unexpected key change.
.sp
The \fI<key description>\fP uses keyctl\-compatible syntax.
This can either be a numeric key ID or a string name in the format \fI%<key type>:<key name>\fP.
See also the \fBKEY IDENTIFIERS\fP section of \fBkeyctl\fP(1).
When no \fI%<key type>:\fP prefix is specified, we assume the key type is \fIuser\fP (default type).
.RE
.SH "REPORTING BUGS"
.sp
Report bugs at \c
.MTO "cryptsetup\(atlists.linux.dev" "cryptsetup mailing list" ""
or in
.URL "https://gitlab.com/cryptsetup/cryptsetup/\-/issues/new" "Issues project section" "."
.sp
Please attach the output of the failed command with \-\-debug option added.
.SH "SEE ALSO"
.sp
.URL "https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions" "Cryptsetup FAQ" ""
.sp
\fBcryptsetup\fP(8), \fBintegritysetup\fP(8) and \fBveritysetup\fP(8)
.SH "CRYPTSETUP"
.sp
Part of \c
.URL "https://gitlab.com/cryptsetup/cryptsetup/" "cryptsetup project" "."