/openbmc/estoraged/include/ |
H A D | cryptsetupInterface.hpp | 68 const char* passphrase, size_t passphraseSize, 86 size_t volumeKeySize, const char* passphrase, 116 const char* passphrase, size_t passphraseSize, uint32_t flags) = 0; 193 const char* passphrase, size_t passphraseSize, in cryptKeyslotChangeByPassphrase() argument 197 cd, keyslotOld, keyslotNew, passphrase, passphraseSize, in cryptKeyslotChangeByPassphrase() 203 const char* passphrase, in cryptKeyslotAddByVolumeKey() argument 207 cd, keyslot, volumeKey, volumeKeySize, passphrase, passphraseSize); in cryptKeyslotAddByVolumeKey() 218 const char* passphrase, size_t passphraseSize, uint32_t flags) override in cryptActivateByPassphrase() argument 220 return crypt_activate_by_passphrase(cd, name, keyslot, passphrase, in cryptActivateByPassphrase()
|
/openbmc/linux/Documentation/driver-api/nvdimm/ |
H 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 …]
|
/openbmc/linux/drivers/acpi/nfit/ |
H 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
|
H 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()
|
/openbmc/openbmc/poky/meta/lib/oe/ |
H A D | gpg_sign.py | 42 def sign_rpms(self, files, keyid, passphrase, digest, sign_chunk, fsk=None, fsk_password=None): argument 46 …ng --batch --passphrase=%s --agent-program=%s|--auto-expand-secmem' % (passphrase, self.gpg_agent_… 64 …def detach_sign(self, input_file, keyid, passphrase_file, passphrase=None, armor=True, output_suff… argument 67 if passphrase_file and passphrase: 88 passphrase = fobj.readline(); 100 (_, stderr) = job.communicate(passphrase.encode("utf-8"))
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-security/passwdqc/ |
H A D | passwdqc_2.0.3.bb | 1 SUMMARY = "A password/passphrase strength checking and enforcement toolset" 3 passwdqc is a password/passphrase strength checking and policy enforcement \ 7 passwd(1). It is capable of checking password or passphrase strength, \ 11 pwqcheck and pwqgen are standalone password/passphrase strength checking \ 12 and random passphrase generator programs, respectively, which are usable \
|
/openbmc/qemu/block/ |
H A D | rbd.c | 344 char **passphrase, in qemu_rbd_convert_luks_options() argument 348 return qcrypto_secret_lookup(luks_opts->key_secret, (uint8_t **)passphrase, in qemu_rbd_convert_luks_options() 355 char **passphrase, in qemu_rbd_convert_luks_create_options() argument 363 passphrase, passphrase_len, errp); in qemu_rbd_convert_luks_create_options() 398 g_autofree char *passphrase = NULL; in qemu_rbd_encryption_format() local 420 &luks_opts.alg, &passphrase, &luks_opts.passphrase_size, in qemu_rbd_encryption_format() 425 luks_opts.passphrase = passphrase; in qemu_rbd_encryption_format() 436 &luks2_opts.alg, &passphrase, &luks2_opts.passphrase_size, in qemu_rbd_encryption_format() 441 luks2_opts.passphrase = passphrase; in qemu_rbd_encryption_format() 479 g_autofree char *passphrase = NULL; in qemu_rbd_encryption_load() local [all …]
|
/openbmc/estoraged/src/test/include/ |
H A D | estoraged_test.hpp | 54 size_t volume_key_size, const char* passphrase, 65 const char* passphrase, size_t passphraseSize, 71 const char* passphrase, size_t passphrase_size,
|
/openbmc/openbmc/meta-security/recipes-ids/tripwire/files/ |
H A D | tripwire.txt | 20 …ic characters for each passphrase. The maximum length of a passphrase is 1023 characters. Quotes s… 22 …passphrase for the site key. The site key passphrase protects the site key, which is used to sign … 24 …e is no way to remove encryption from a signed file if you forget your passphrase. If you forget t…
|
H A D | twinstall.sh | 285 --local-passphrase $TW_LOCAL_PASS 2> /dev/null
|
/openbmc/openbmc/poky/meta/recipes-support/pinentry/ |
H A D | pinentry_1.3.1.bb | 1 SUMMARY = "Collection of simple PIN or passphrase entry dialogs" 3 Pinentry is a collection of simple PIN or passphrase entry dialogs which \
|
/openbmc/linux/drivers/net/wireless/marvell/mwifiex/ |
H 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()
|
/openbmc/openbmc/poky/meta/recipes-connectivity/wpa-supplicant/ |
H A D | wpa-supplicant_2.11.bb | 104 PACKAGE_BEFORE_PN += "${PN}-passphrase ${PN}-cli" 112 FILES:${PN}-passphrase = "${sbindir}/wpa_passphrase" 120 RRECOMMENDS:${PN} = "${PN}-passphrase ${PN}-cli ${PN}-plugins"
|
/openbmc/linux/Documentation/process/ |
H A 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 …]
|
/openbmc/linux/Documentation/translations/it_IT/process/ |
H A 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 …]
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 288 | 46 SECRET=secret,id=sec0,data=passphrase
|
H A D | 082.out | 65 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 91 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 117 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 143 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 169 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 195 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 221 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 247 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 288 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase 375 encrypt.key-secret=<str> - ID of secret providing qcow AES key or LUKS passphrase [all …]
|
/openbmc/openbmc/meta-security/recipes-security/fscryptctl/ |
H A D | fscryptctl_1.1.0.bb | 5 generation, key wrapping, PAM integration, and passphrase hashing, see \
|
/openbmc/linux/tools/testing/nvdimm/test/ |
H 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 …]
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | sign_ipk.bbclass | 11 # Path to a file containing the passphrase of the signing key.
|
H A D | sign_package_feed.bbclass | 12 # Path to a file containing the passphrase of the signing key.
|
H A D | sign_rpm.bbclass | 11 # The passphrase of the signing key.
|
/openbmc/qemu/docs/system/ |
H A D | qemu-block-drivers.rst.inc | 68 qcow2 header) be encrypted using the LUKS format. The passphrase to 81 - The user passphrase is directly used as the encryption key. A poorly 82 chosen or short passphrase will compromise the security of the encryption. 83 - In the event of the passphrase being compromised there is no way to 84 change the passphrase to protect data in any qcow images. The files must 85 be cloned, using a different encryption passphrase in the new file. The 96 Provides the ID of a ``secret`` object that contains the passphrase 256 Provides the ID of a ``secret`` object that contains the passphrase.
|
/openbmc/linux/Documentation/filesystems/ |
H A D | ecryptfs.rst | 50 You should be prompted for a passphrase and a salt (the salt may be
|
/openbmc/linux/Documentation/security/keys/ |
H A D | ecryptfs.rst | 11 using a key, the FEKEK, derived from a user prompted passphrase; in the latter
|