1CRYPTSETUP-LUKSKILLSLOT(8)   Maintenance Commands   CRYPTSETUP-LUKSKILLSLOT(8)
2
3
4

NAME

6       cryptsetup-luksKillSlot - wipe a key-slot from the LUKS device
7

SYNOPSIS

9       cryptsetup luksKillSlot [<options>] <device> <key slot number>
10

DESCRIPTION

12       Wipe the key-slot number <key slot> from the LUKS device. Except
13       running in batch-mode (-q) a remaining passphrase must be supplied,
14       either interactively or via --key-file. This command can remove the
15       last remaining key-slot, but requires an interactive confirmation when
16       doing so. Removing the last passphrase makes a LUKS container
17       permanently inaccessible.
18
19       <options> can be [--key-file, --keyfile-offset, --keyfile-size,
20       --header, --disable-locks, --type, --verify-passphrase, --timeout].
21
22       WARNING: If you read the passphrase from stdin (without further
23       argument or with '-' as an argument to --key-file), batch-mode (-q)
24       will be implicitly switched on and no warning will be given when you
25       remove the last remaining passphrase from a LUKS container. Removing
26       the last passphrase makes the LUKS container permanently inaccessible.
27
28       NOTE: If there is no passphrase provided (on stdin or through
29       --key-file argument) and batch-mode (-q) is active, the key-slot is
30       removed without any other warning.
31

OPTIONS

33       --type <device-type>
34           Specifies required device type, for more info read BASIC ACTIONS
35           section in cryptsetup(8).
36
37       --verify-passphrase, -y
38           When interactively asking for a passphrase, ask for it twice and
39           complain if both inputs do not match. Ignored on input from file or
40           stdin.
41
42       --key-file, -d name
43           Read the passphrase from file.
44
45           If the name given is "-", then the passphrase will be read from
46           stdin. In this case, reading will not stop at newline characters.
47
48           See section NOTES ON PASSPHRASE PROCESSING in cryptsetup(8) for
49           more information.
50
51       --keyfile-offset value
52           Skip value bytes at the beginning of the key file.
53
54       --keyfile-size, -l value
55           Read a maximum of value bytes from the key file. The default is to
56           read the whole file up to the compiled-in maximum that can be
57           queried with --help. Supplying more data than the compiled-in
58           maximum aborts the operation.
59
60           This option is useful to cut trailing newlines, for example. If
61           --keyfile-offset is also given, the size count starts after the
62           offset.
63
64       --timeout, -t <number of seconds>
65           The number of seconds to wait before timeout on passphrase input
66           via terminal. It is relevant every time a passphrase is asked. It
67           has no effect if used in conjunction with --key-file.
68
69           This option is useful when the system should not stall if the user
70           does not input a passphrase, e.g. during boot. The default is a
71           value of 0 seconds, which means to wait forever.
72
73       --header <device or file storing the LUKS header>
74           Use a detached (separated) metadata device or file where the LUKS
75           header is stored. This option allows one to store ciphertext and
76           LUKS header on different devices.
77
78           For commands that change the LUKS header (e.g. luksAddKey), specify
79           the device or file with the LUKS header directly as the LUKS
80           device.
81
82       --disable-locks
83           Disable lock protection for metadata on disk. This option is valid
84           only for LUKS2 and ignored for other formats.
85
86           WARNING: Do not use this option unless you run cryptsetup in a
87           restricted environment where locking is impossible to perform
88           (where /run directory cannot be used).
89
90       --batch-mode, -q
91           Suppresses all confirmation questions. Use with care!
92
93           If the --verify-passphrase option is not specified, this option
94           also switches off the passphrase verification.
95
96       --debug or --debug-json
97           Run in debug mode with full diagnostic logs. Debug output lines are
98           always prefixed by #.
99
100           If --debug-json is used, additional LUKS2 JSON data structures are
101           printed.
102
103       --version, -V
104           Show the program version.
105
106       --usage
107           Show short option help.
108
109       --help, -?
110           Show help text and default parameters.
111

REPORTING BUGS

113       Report bugs at cryptsetup mailing list <cryptsetup@lists.linux.dev> or
114       in Issues project section
115       <https://gitlab.com/cryptsetup/cryptsetup/-/issues/new>.
116
117       Please attach output of the failed command with --debug option added.
118

SEE ALSO

120       Cryptsetup FAQ
121       <https://gitlab.com/cryptsetup/cryptsetup/wikis/FrequentlyAskedQuestions>
122
123       cryptsetup(8), integritysetup(8) and veritysetup(8)
124

CRYPTSETUP

126       Part of cryptsetup project <https://gitlab.com/cryptsetup/cryptsetup/>.
127
128
129
130cryptsetup 2.6.1                  2023-02-10        CRYPTSETUP-LUKSKILLSLOT(8)
Impressum