Skip to content

Latest commit

 

History

History
52 lines (40 loc) · 2.05 KB

cryptsetup-luksChangeKey.8.adoc

File metadata and controls

52 lines (40 loc) · 2.05 KB

cryptsetup-luksChangeKey(8) Manual Page

NAME

cryptsetup-luksChangeKey - change an existing passphrase

SYNOPSIS

cryptsetup luksChangeKey [<options>] <device> [<new key file>]

DESCRIPTION

Changes an existing passphrase. The passphrase to be changed must be supplied interactively or via --key-file. The new passphrase can be supplied interactively or in a file given as the positional argument.

If a key-slot is specified (via --key-slot), the passphrase for that key-slot must be given and the new passphrase will overwrite the specified key-slot. If no key-slot is specified and there is still a free key-slot, then the new passphrase will be put into a free key-slot before the key-slot containing the old passphrase is purged. If there is no free key-slot, then the key-slot with the old passphrase is overwritten directly.

WARNING: If a key-slot is overwritten, a media failure during this operation can cause the overwrite to fail after the old passphrase has been wiped and make the LUKS container inaccessible. LUKS2 mitigates that by never overwriting existing keyslot area as long as there’s a free space in keyslots area at least for one more LUKS2 keyslot.

WARNING: If you need to use both luksChangeKey and reencrypt (e.g. to recover from a leak) you need to use them in that order to not leak the new volume key.

NOTE: some parameters are effective only if used with LUKS2 format that supports per-keyslot parameters. For LUKS1, PBKDF type and hash algorithm is always the same for all keyslots.

<options> can be [--key-file, --keyfile-offset, --keyfile-size, --new-keyfile-offset, --iter-time, --pbkdf, --pbkdf-force-iterations, --pbkdf-memory, --pbkdf-parallel, --new-keyfile-size, --key-slot, --force-password, --hash, --header, --disable-locks, --type, --keyslot-cipher, --keyslot-key-size, --timeout, --verify-passphrase].