Home
last modified time | relevance | path

Searched refs:passphrase (Results 1 – 17 of 17) sorted by relevance

/Linux-v5.4/drivers/acpi/nfit/
Dintel.h77 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
Dintel.c174 memcpy(nd_cmd.cmd.passphrase, key_data->data, in intel_security_unlock()
175 sizeof(nd_cmd.cmd.passphrase)); in intel_security_unlock()
215 memcpy(nd_cmd.cmd.passphrase, key_data->data, in intel_security_disable()
216 sizeof(nd_cmd.cmd.passphrase)); in intel_security_disable()
260 memcpy(nd_cmd.cmd.passphrase, key->data, in intel_security_erase()
261 sizeof(nd_cmd.cmd.passphrase)); in intel_security_erase()
343 memcpy(nd_cmd.cmd.passphrase, nkey->data, in intel_security_overwrite()
344 sizeof(nd_cmd.cmd.passphrase)); in intel_security_overwrite()
/Linux-v5.4/Documentation/driver-api/nvdimm/
Dsecurity.rst10 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-v5.4/drivers/net/wireless/marvell/mwifiex/
Duap_cmd.c312 struct host_cmd_tlv_passphrase *passphrase; in mwifiex_uap_bss_wpa() local
363 passphrase = (struct host_cmd_tlv_passphrase *)tlv; in mwifiex_uap_bss_wpa()
364 passphrase->header.type = in mwifiex_uap_bss_wpa()
366 passphrase->header.len = cpu_to_le16(bss_cfg->wpa_cfg.length); in mwifiex_uap_bss_wpa()
367 memcpy(passphrase->passphrase, bss_cfg->wpa_cfg.passphrase, in mwifiex_uap_bss_wpa()
Dioctl.h72 u8 passphrase[MWIFIEX_WPA_PASSHPHRASE_LEN]; member
Dfw.h1959 u8 passphrase[0]; member
/Linux-v5.4/Documentation/process/
Dmaintainer-pgp-guide.rst99 of caching the private key passphrase. There are two options you should
100 know in order to tweak when the passphrase should be expired from cache:
106 the key since initial passphrase entry, if the maximum time-to-live
107 countdown expires, you'll have to enter the passphrase again. The
202 Ensure your passphrase is strong
208 obtaining the passphrase to decrypt them.
211 strong passphrase. To set it or change it, use::
213 $ gpg --change-passphrase [fpr]
266 pen and write your passphrase on the margin of the paper. **This is
268 that passphrase, and if you ever change it you will not remember what it
[all …]
/Linux-v5.4/Documentation/translations/it_IT/process/
Dmaintainer-pgp-guide.rst107 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-v5.4/tools/testing/nvdimm/test/
Dnfit.c142 u8 passphrase[32]; member
967 } else if (memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_unlock_unit()
991 } else if (memcmp(nd_cmd->old_pass, sec->passphrase, in nd_intel_test_cmd_set_pass()
996 memcpy(sec->passphrase, nd_cmd->new_pass, in nd_intel_test_cmd_set_pass()
1036 } else if (memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_disable_pass()
1041 memset(sec->passphrase, 0, ND_INTEL_PASSPHRASE_SIZE); in nd_intel_test_cmd_disable_pass()
1059 } else if (memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_secure_erase()
1065 && (memcmp(nd_cmd->passphrase, zero_key, in nd_intel_test_cmd_secure_erase()
1070 memset(sec->passphrase, 0, ND_INTEL_PASSPHRASE_SIZE); in nd_intel_test_cmd_secure_erase()
1088 memcmp(nd_cmd->passphrase, sec->passphrase, in nd_intel_test_cmd_overwrite()
[all …]
/Linux-v5.4/Documentation/filesystems/
Decryptfs.txt44 You should be prompted for a passphrase and a salt (the salt may be
Dfscrypt.rst201 as a passphrase, it is critical that a KDF designed for this purpose
599 from a passphrase or other low-entropy user credential.
919 to be added before prompting the user for the passphrase needed to
Dubifs-authentication.rst406 Nevertheless, it will be possible for a user to provide a single passphrase
/Linux-v5.4/Documentation/security/keys/
Decryptfs.rst11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
/Linux-v5.4/Documentation/power/
Dswsusp-dmcrypt.rst23 have to be able to either enter a passphrase or that you read
/Linux-v5.4/Documentation/kbuild/
Dkbuild.rst223 This variable allows a passphrase or PIN to be passed to the sign-file
/Linux-v5.4/Documentation/admin-guide/
Dmodule-signing.rst232 If the private key requires a passphrase or PIN, it can be provided in the
/Linux-v5.4/drivers/net/wireless/ath/wil6210/
Dwmi.h415 u8 passphrase[WMI_PASSPHRASE_LEN]; member