mirror of
https://gitlab.com/cryptsetup/cryptsetup.git
synced 2025-12-12 19:30:04 +01:00
51a1e218cf
We can not link internal VK kernel key in custom user keyring. There are two reasons for it: The internal VK kernel key description can not be acquired via API and it may change over time (LUKS2 reencryption). With recent SED OPAL support volume key becomes a 'blob' containing up to two keys (dm-crypt key for SWE and key for unlocking SED OPAL locking range). The internal kernel key contains only dm-crypt (if required) but custom user keyring needs to be provided with whole volume key (blob). Added user specified key description for the linked key in custom user keyring. The linked key can be reached by the specified description after successful activation (resume).
30 lines
868 B
Plaintext
30 lines
868 B
Plaintext
= cryptsetup-luksResume(8)
|
|
:doctype: manpage
|
|
:manmanual: Maintenance Commands
|
|
:mansource: cryptsetup {release-version}
|
|
:man-linkstyle: pass:[blue R < >]
|
|
:COMMON_OPTIONS:
|
|
:ACTION_LUKSRESUME:
|
|
|
|
== Name
|
|
|
|
cryptsetup-luksResume - resume a suspended device and reinstate the key
|
|
|
|
== SYNOPSIS
|
|
|
|
*cryptsetup _luksResume_ [<options>] <name>*
|
|
|
|
== DESCRIPTION
|
|
|
|
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.
|
|
|
|
*<options>* 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].
|
|
|
|
include::man/common_options.adoc[]
|
|
include::man/common_footer.adoc[]
|