/linux-6.3-rc2/Documentation/driver-api/nvdimm/ |
A 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-6.3-rc2/drivers/acpi/nfit/ |
A 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
|
A 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-6.3-rc2/drivers/net/wireless/marvell/mwifiex/ |
A 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()
|
A D | ioctl.h | 60 u8 passphrase[MWIFIEX_WPA_PASSHPHRASE_LEN]; member
|
A D | fw.h | 1956 u8 passphrase[]; member
|
/linux-6.3-rc2/Documentation/process/ |
A D | maintainer-pgp-guide.rst | 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 241 your passphrase, printing out even to "cloud-integrated" modern 262 For the encryption passphrase, you can use the same one as on your 356 passphrase or adding a subkey, should automatically convert the old [all …]
|
/linux-6.3-rc2/Documentation/translations/it_IT/process/ |
A D | maintainer-pgp-guide.rst | 107 individuare la passphrase. Ci sono due opzioni che dovreste conoscere 108 per personalizzare la scadenza della passphrase nella cache: 115 uso della chiave da quando avete inserito la passphrase, se il massimo 116 time-to-live è scaduto, dovrete reinserire nuovamente la passphrase. 212 Assicuratevi che la vostra passphrase sia forte 219 aver prima ottenuto la passphrase per decriptarle. 222 una passphrase forte. Per impostarla o cambiarla, usate:: 224 $ gpg --change-passphrase [fpr] 277 la passphrase, e se mai doveste cambiarla non vi ricorderete qual'era al 280 Mettete la copia cartacea e la passphrase scritta a mano in una busta e [all …]
|
/linux-6.3-rc2/tools/testing/nvdimm/test/ |
A 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-6.3-rc2/Documentation/filesystems/ |
A D | ecryptfs.rst | 50 You should be prompted for a passphrase and a salt (the salt may be
|
A D | fscrypt.rst | 201 as a passphrase, it is critical that a KDF designed for this purpose 674 from a passphrase or other low-entropy user credential. 1033 to be added before prompting the user for the passphrase needed to
|
A D | ubifs-authentication.rst | 410 Nevertheless, it will be possible for a user to provide a single passphrase
|
/linux-6.3-rc2/Documentation/security/keys/ |
A D | ecryptfs.rst | 11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
|
/linux-6.3-rc2/Documentation/power/ |
A D | swsusp-dmcrypt.rst | 23 have to be able to either enter a passphrase or that you read
|
/linux-6.3-rc2/Documentation/kbuild/ |
A D | kbuild.rst | 251 This variable allows a passphrase or PIN to be passed to the sign-file
|
/linux-6.3-rc2/Documentation/admin-guide/ |
A D | module-signing.rst | 232 If the private key requires a passphrase or PIN, it can be provided in the
|
/linux-6.3-rc2/drivers/net/wireless/ath/wil6210/ |
A D | wmi.h | 405 u8 passphrase[WMI_PASSPHRASE_LEN]; member
|