| /Linux-v6.6/Documentation/driver-api/nvdimm/ |
| D | security.rst | 10 security DSMs: "get security state", "set passphrase", "disable passphrase",
28 update <old_keyid> <new_keyid> - enable or update passphrase.
33 master_update <keyid> <new_keyid> - enable or update master passphrase.
42 The DIMM id would be provided along with the key payload (passphrase) to
46 key "passphrase" is expected to be 32bytes long. This is similar to the ATA
66 the passphrase for the respective nvdimms. It is also recommended that the
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
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
[all …]
|
| /Linux-v6.6/drivers/acpi/nfit/ |
| D | intel.h | 77 u8 passphrase[ND_INTEL_PASSPHRASE_SIZE]; member
82 u8 passphrase[ND_INTEL_PASSPHRASE_SIZE]; member
91 u8 passphrase[ND_INTEL_PASSPHRASE_SIZE]; member
96 u8 passphrase[ND_INTEL_PASSPHRASE_SIZE]; member
111 u8 passphrase[ND_INTEL_PASSPHRASE_SIZE]; member
|
| D | intel.c | 215 memcpy(nd_cmd.cmd.passphrase, key_data->data, in intel_security_unlock()
216 sizeof(nd_cmd.cmd.passphrase)); in intel_security_unlock()
253 memcpy(nd_cmd.cmd.passphrase, key_data->data, in intel_security_disable()
254 sizeof(nd_cmd.cmd.passphrase)); in intel_security_disable()
296 memcpy(nd_cmd.cmd.passphrase, key->data, in intel_security_erase()
297 sizeof(nd_cmd.cmd.passphrase)); in intel_security_erase()
373 memcpy(nd_cmd.cmd.passphrase, nkey->data, in intel_security_overwrite()
374 sizeof(nd_cmd.cmd.passphrase)); in intel_security_overwrite()
|
| /Linux-v6.6/drivers/net/wireless/marvell/mwifiex/ |
| D | uap_cmd.c | 301 struct host_cmd_tlv_passphrase *passphrase; in mwifiex_uap_bss_wpa() local
352 passphrase = (struct host_cmd_tlv_passphrase *)tlv; in mwifiex_uap_bss_wpa()
353 passphrase->header.type = in mwifiex_uap_bss_wpa()
355 passphrase->header.len = cpu_to_le16(bss_cfg->wpa_cfg.length); in mwifiex_uap_bss_wpa()
356 memcpy(passphrase->passphrase, bss_cfg->wpa_cfg.passphrase, in mwifiex_uap_bss_wpa()
|
| D | ioctl.h | 60 u8 passphrase[MWIFIEX_WPA_PASSHPHRASE_LEN]; member
|
| D | fw.h | 1956 u8 passphrase[]; member
|
| /Linux-v6.6/Documentation/process/ |
| D | maintainer-pgp-guide.rst | 81 of caching the private key passphrase. There are two options you should
82 know in order to tweak when the passphrase should be expired from cache:
88 the key since initial passphrase entry, if the maximum time-to-live
89 countdown expires, you'll have to enter the passphrase again. The
180 Ensure your passphrase is strong
186 obtaining the passphrase to decrypt them.
189 strong passphrase. To set it or change it, use::
191 $ gpg --change-passphrase [fpr]
228 pen and write your passphrase on the margin of the paper. **This is
230 that passphrase, and if you ever change it you will not remember what it
[all …]
|
| /Linux-v6.6/Documentation/translations/it_IT/process/ |
| D | maintainer-pgp-guide.rst | 89 individuare la passphrase. Ci sono due opzioni che dovreste conoscere
90 per personalizzare la scadenza della passphrase nella cache:
97 uso della chiave da quando avete inserito la passphrase, se il massimo
98 time-to-live è scaduto, dovrete reinserire nuovamente la passphrase.
189 Assicuratevi che la vostra passphrase sia forte
196 aver prima ottenuto la passphrase per decriptarle.
199 una passphrase forte. Per impostarla o cambiarla, usate::
201 $ gpg --change-passphrase [fpr]
244 la passphrase, e se mai doveste cambiarla non vi ricorderete qual'era al
247 Mettete la copia cartacea e la passphrase scritta a mano in una busta e
[all …]
|
| /Linux-v6.6/tools/testing/nvdimm/test/ |
| D | nfit.c | 140 u8 passphrase[32]; member
969 } else if (memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_unlock_unit()
993 } else if (memcmp(nd_cmd->old_pass, sec->passphrase, in nd_intel_test_cmd_set_pass()
998 memcpy(sec->passphrase, nd_cmd->new_pass, in nd_intel_test_cmd_set_pass()
1038 } else if (memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_disable_pass()
1043 memset(sec->passphrase, 0, ND_INTEL_PASSPHRASE_SIZE); in nd_intel_test_cmd_disable_pass()
1061 } else if (memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_secure_erase()
1067 && (memcmp(nd_cmd->passphrase, zero_key, in nd_intel_test_cmd_secure_erase()
1072 memset(sec->passphrase, 0, ND_INTEL_PASSPHRASE_SIZE); in nd_intel_test_cmd_secure_erase()
1090 memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_overwrite()
[all …]
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | ecryptfs.rst | 50 You should be prompted for a passphrase and a salt (the salt may be
|
| D | fscrypt.rst | 201 as a passphrase, it is critical that a KDF designed for this purpose
748 from a passphrase or other low-entropy user credential.
1107 to be added before prompting the user for the passphrase needed to
|
| D | ubifs-authentication.rst | 410 Nevertheless, it will be possible for a user to provide a single passphrase
|
| /Linux-v6.6/Documentation/security/keys/ |
| D | ecryptfs.rst | 11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
|
| /Linux-v6.6/Documentation/power/ |
| D | swsusp-dmcrypt.rst | 23 have to be able to either enter a passphrase or that you read
|
| /Linux-v6.6/Documentation/kbuild/ |
| D | kbuild.rst | 257 This variable allows a passphrase or PIN to be passed to the sign-file
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | module-signing.rst | 232 If the private key requires a passphrase or PIN, it can be provided in the
|
| /Linux-v6.6/drivers/net/wireless/ath/wil6210/ |
| D | wmi.h | 405 u8 passphrase[WMI_PASSPHRASE_LEN]; member
|
