Lines Matching refs:key

29 disable <keyid> - disable enabled security and remove key.
31 erase <keyid> - delete existing user encryption key.
34 master_erase <keyid> - delete existing user encryption key.
39 The key is associated to the payload by the DIMM id. For example:
42 The DIMM id would be provided along with the key payload (passphrase) to
45 The security keys are managed on the basis of a single key per DIMM. The
46 key "passphrase" is expected to be 32bytes long. This is similar to the ATA
47 security specification [2]. A key is initially acquired via the request_key()
51 A nvdimm encrypted-key of format enc32 has the description format of:
55 encrypted-keys of enc32 format. TPM usage with a master trusted key is
61 retrieve the key from the kernel user keyring. This is the only time
71 When doing an update, it is expected that the existing key is removed from
72 the kernel user keyring and reinjected as different (old) key. It's irrelevant
73 what the key description is for the old key since we are only interested in the
74 keyid when doing the update operation. It is also expected that the new key
93 An key with the current passphrase payload that is tied to the nvdimm should be
101 An key with the current passphrase payload that is tied to the nvdimm should be
109 Overwrite can be done without a key if security is not enabled. A key serial
110 of 0 can be passed in to indicate no key.
115 An encrypted-key with the current user passphrase that is tied to the nvdimm
124 master passphrase key is passed to the kernel. The master passphrase key
125 is just another encrypted-key.
135 passphrase key is passed to the kernel. The master passphrase key is just
136 another encrypted-key.