1CLEVIS-LUKS-BIND(1)                                        CLEVIS-LUKS-BIND(1)
2
3
4

NAME

6       clevis-luks-bind - Bind a LUKS device using the specified policy
7

SYNOPSIS

9       clevis luks bind [-f] [-y] -d DEV [-t TKN_ID] [-s SLT] [-k KEY] PIN CFG
10

OVERVIEW

12       The clevis luks bind command binds a LUKS device using the specified
13       policy. This is accomplished with a simple command:
14
15           $ clevis luks bind -d /dev/sda tang '{"url":...}'
16
17       This command performs four steps:
18
19        1. Creates a new key with the same entropy as the LUKS master key.
20
21        2. Encrypts the new key with Clevis.
22
23        3. Stores the Clevis JWE in the LUKS header.
24
25        4. Enables the new key for use with LUKS.
26
27       This disk can now be unlocked with your existing password as well as
28       with the Clevis policy. You will additionally need to enable one or
29       more of the Clevis LUKS unlockers. See clevis-luks-unlockers(7).
30

OPTIONS

32       •   -f : Do not prompt for LUKSMeta initialization
33
34       •   -y : Automatically answer yes for all questions. When using tang,
35           it causes the advertisement trust check to be skipped, which can be
36           useful in automated deployments
37
38       •   -d DEV : The LUKS device on which to perform binding
39
40       •   -s SLT : The LUKSMeta slot to use for metadata storage
41
42       •   -t TKN_ID : The LUKS token ID to use; only available for LUKS2
43
44       •   -k KEY : Non-interactively read LUKS password from KEY file
45
46       •   -k - : Non-interactively read LUKS password from standard input
47

CAVEATS

49       This command does not change the LUKS master key. This implies that if
50       you create a LUKS-encrypted image for use in a Virtual Machine or Cloud
51       environment, all the instances that run this image will share a master
52       key. This is extremely dangerous and should be avoided at all cost.
53
54       This is not a limitation of Clevis but a design principle of LUKS. If
55       you wish to have encrypted root volumes in the cloud, you will need to
56       make sure that you perform the OS install method for each instance in
57       the cloud as well. The images cannot be shared without also sharing a
58       master key.
59

SEE ALSO

61       clevis-luks-unlockers(7), clevis-encrypt-tang(1),
62       clevis-encrypt-sss(1), clevis-decrypt(1)
63
64
65
66                                  04/15/2021               CLEVIS-LUKS-BIND(1)
Impressum