Home
last modified time | relevance | path

Searched full:encrypted (Results 1 – 25 of 170) sorted by relevance

1234567

/openbmc/u-boot/doc/imx/habv4/guides/
H A Dencrypted_boot.txt1 1. Setup U-Boot Image for Encrypted Boot
4 Encrypted Boot. The image is encrypted by i.MX Code Signing
6 u-boot-dtb.imx with the encrypted data. The Initial Vector Table,
9 The image data is encrypted with a Encryption Key (DEK).
22 Note: The encrypted boot feature is only supported by HABv4 or
31 The resulting DEK blob then is used to construct the encrypted
39 cat u-boot-signed-pad.imx DEK_blob.bin > u-boot-encrypted.imx
/openbmc/qemu/target/s390x/
H A Dcpu_features_def.h.inc241 DEF_FEAT(KMAC_EDEA, "kmac-edea", KMAC, 9, "KMAC Encrypted-DEA")
242 DEF_FEAT(KMAC_ETDEA_128, "kmac-etdea-128", KMAC, 10, "KMAC Encrypted-TDEA-128")
243 DEF_FEAT(KMAC_ETDEA_192, "kmac-etdea-192", KMAC, 11, "KMAC Encrypted-TDEA-192")
247 DEF_FEAT(KMAC_EAES_128, "kmac-eaes-128", KMAC, 26, "KMAC Encrypted-AES-128")
248 DEF_FEAT(KMAC_EAES_192, "kmac-eaes-192", KMAC, 27, "KMAC Encrypted-AES-192")
249 DEF_FEAT(KMAC_EAES_256, "kmac-eaes-256", KMAC, 28, "KMAC Encrypted-AES-256")
254 DEF_FEAT(KMAC_HMAC_ESHA_224, "kmac-hmac-esha-224", KMAC, 120, "KMAC HMAC-Encrypted-SHA-224")
255 DEF_FEAT(KMAC_HMAC_ESHA_256, "kmac-hmac-esha-246", KMAC, 121, "KMAC HMAC-Encrypted-SHA-256")
256 DEF_FEAT(KMAC_HMAC_ESHA_384, "kmac-hmac-esha-384", KMAC, 122, "KMAC HMAC-Encrypted-SHA-384")
257 DEF_FEAT(KMAC_HMAC_ESHA_512, "kmac-hmac-esha-512", KMAC, 123, "KMAC HMAC-Encrypted-SHA-512")
[all …]
/openbmc/phosphor-net-ipmid/
H A Dcrypt_algo.hpp18 * algorithm field that is used for encrypted payload data under the session.
19 * The ‘encrypted’ bit in the payload type field being set identifies packets
20 * with payloads that include data that is encrypted per this specification.
21 * When payload data is encrypted, there may be additional “Confidentiality
60 * @param[in] payloadLen - Length of the encrypted IPMI payload
73 * @return encrypted payload if the operation is successful
117 * encrypted one block at a time from the lowest data offset to the highest
158 * @param[in] payloadLen - Length of the encrypted IPMI payload
171 * @return encrypted payload if the operation is successful
196 * @return encrypted data if the operation is successful
/openbmc/docs/designs/
H A Destoraged.md1 # eStoraged Design - Encrypted Secondary Storage Management Daemon
15 This daemon will serve as an abstraction for an encrypted storage device,
17 manage the encrypted filesystem on the device. Using the D-Bus interface, other
19 encrypted filesystem, wipe its contents, lock/unlock the device, or change the
57 - Create a new LUKS encrypted filesystem on the device
76 client daemon on the BMC will interact with eStoraged to set up a new encrypted
108 To manage the encrypted filesystem, we will make use of the
134 encrypted filesystem), the D-Bus interface will be asynchronous, with the
143 is often used to unlock an encrypted block device, where it takes the password
150 for each storage device in a system. It is capable of setting up an encrypted
[all …]
/openbmc/estoraged/
H A DREADME.md3 This daemon serves as an abstraction for an encrypted storage device,
5 manage the encrypted filesystem on the device. Using the D-Bus interface, other
7 encrypted filesystem, wipe its contents, lock/unlock the device, or change the
/openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-linux-distros/files/unattended-boot-conf/openSUSE/
H A Dautoinst.xml592 <encrypted t="boolean">true</encrypted>
611 <encrypted t="boolean">true</encrypted>
630 <encrypted t="boolean">true</encrypted>
649 <encrypted t="boolean">true</encrypted>
668 <encrypted t="boolean">true</encrypted>
687 <encrypted t="boolean">true</encrypted>
706 <encrypted t="boolean">true</encrypted>
725 <encrypted t="boolean">true</encrypted>
744 <encrypted t="boolean">true</encrypted>
763 <encrypted t="boolean">true</encrypted>
[all …]
/openbmc/qemu/docs/system/i386/
H A Damd-memory-encryption.rst3 AMD Secure Encrypted Virtualization (SEV)
6 Secure Encrypted Virtualization (SEV) is a feature found on AMD processors.
8 SEV is an extension to the AMD-V architecture which supports running encrypted
9 virtual machines (VMs) under the control of KVM. Encrypted VMs have their pages
11 unencrypted version. Each encrypted VM is associated with a unique encryption
13 encrypted guests data will be incorrectly decrypted, leading to unintelligible
20 encrypted guest. These SEV commands can be issued via KVM_MEMORY_ENCRYPT_OP
23 Secure Encrypted Virtualization - Encrypted State (SEV-ES) builds on the SEV
33 Boot images (such as bios) must be encrypted before a guest can be booted. The
84 ``LAUNCH_MEASURE`` can be used to retrieve the measurement of encrypted memory and,
[all …]
/openbmc/qemu/tests/qemu-iotests/
H A D191.out146 "encrypted": false,
175 "encrypted": false,
217 "encrypted": false,
246 "encrypted": false,
288 "encrypted": false,
317 "encrypted": false,
347 "encrypted": false,
376 "encrypted": false,
561 "encrypted": false,
590 "encrypted": false,
[all …]
H A D087.out35 === Encrypted image QCow ===
42 {"error": {"class": "GenericError", "desc": "Use of AES-CBC encrypted IMGFMT images is no longer su…
47 === Encrypted image LUKS ===
H A D2954 # Test case QMP's encrypted key management
75 # create the encrypted block device
89 # open an encrypted block device
118 # close the encrypted block device
123 # add a key to an encrypted block device
162 # erase a key from an encrypted block device
273 # Encrypted formats support
H A D273.out65 "encrypted": false,
94 "encrypted": false,
135 "encrypted": false,
164 "encrypted": false,
193 "encrypted": false,
H A D29674 # create the encrypted block device using qemu-img
115 # open an encrypted block device
151 # close the encrypted block device
157 # add a key to an encrypted block device
276 # support only raw luks since luks encrypted qcow2 is a proper
/openbmc/openbmc/meta-security/meta-integrity/data/debug-keys/
H A Dima-local-ca.priv1 -----BEGIN ENCRYPTED PRIVATE KEY-----
7 -----END ENCRYPTED PRIVATE KEY-----
/openbmc/qemu/docs/specs/
H A Dppc-spapr-uv-hcalls.rst32 SVM file systems are encrypted using a symmetric key. This key is then
33 wrapped/encrypted using the public key of a trusted system which has the private
39 host system boot. All sensitive in and out values will be encrypted using the
41 any sensitive contents will generally be encrypted using this session key.
/openbmc/u-boot/board/xilinx/zynq/
H A DKconfig14 bool "Enable zynq aes command for decryption of encrypted images"
18 Decrypts the encrypted image present in source address
/openbmc/openbmc/meta-phosphor/recipes-phosphor/storage/
H A Destoraged_git.bb1 SUMMARY = "Encrypted storage management daemon"
2 DESCRIPTION = "Provides a D-Bus interface to manage an encrypted storage device"
/openbmc/qemu/tests/qemu-iotests/tests/
H A Dqcow2-encryption.out3 === Create an encrypted image ===
19 encrypted: yes
/openbmc/phosphor-host-ipmid/user_channel/
H A Dpasswd_mgr.hpp78 /** @brief initializes passwdMapList by reading the encrypted file
86 /** @brief Function to read the encrypted password file data
112 * @param[in] inBytes - input data to be encrypted / decrypted
113 * @param[in] inBytesLen - input size to be encrypted / decrypted
/openbmc/qemu/docs/system/s390x/
H A Dprotvirt.rst5 (PVMs) are encrypted or inaccessible to the hypervisor, effectively
7 encrypted and can only be decrypted by the firmware, represented by an
62 from the disk boot. This memory layout includes the encrypted
/openbmc/u-boot/doc/imx/habv4/
H A Dintroduction_habv4.txt2 + i.MX Secure and Encrypted Boot using HABv4 +
71 1.2 The HABv4 Encrypted Boot Architecture
74 The HAB Encrypted Boot feature available in CAAM supported devices adds an
83 second mechanism is the digital signature, which authenticates the encrypted
86 Keep in mind that the encrypted boot makes use of both mechanisms whatever the
89 boot data and DCD) which can only be signed, not encrypted.
91 The diagram below illustrate the encrypted boot process overview:
133 During the design of encrypted boot using DEK blob, it is necessary to inhibit
141 encrypted boot guide and application note AN12056[3] .
262 [3] AN12056: "Encrypted Boot on HABv4 and CAAM Enabled Devices" - Rev. 1
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/polkit/files/
H A D50-org.freedesktop.udiskie.rules11 "org.freedesktop.udisks2.encrypted-unlock": YES,
17 "org.freedesktop.udisks2.encrypted-unlock-other-seat": YES,
/openbmc/qemu/tests/functional/
H A Dtest_arm_max78000fthr.py43 'encrypted to : a47ca9dd e0df4c86 a070af6e 91710dec')
45 'encrypted to : cab7a28e bf456751 9049fcea 8960494b')
/openbmc/pam-ipmi/src/pam_ipmisave/
H A Dpam_ipmisave.c46 * Meta data struct for storing the encrypted password file
47 * Note: Followed by this structure, the real data of hash, iv, encrypted data
136 * @param[in] inbytes - buffer which has to be encrypted or decrypted.
138 * @param[in] outbytes - buffer to store decrypted or encrypted data.
170 // calculate MAC for the encrypted message. in encrypt_decrypt_data()
220 // Create MAC for the encrypted message. in encrypt_decrypt_data()
261 * username in encrypted form along with meta data
267 * @param[in] towhat - password that has to stored in encrypted form
520 // Buffer to store encrypted message. in update_pass_special_file()
550 // Write the meta password structure, followed by hash, iv, encrypted in update_pass_special_file()
[all …]
/openbmc/qemu/include/crypto/
H A Dsecret.h55 * The data may be optionally encrypted with AES-256-CBC,
83 * Each secret to be encrypted needs to have a random
90 * A secret to be defined can now be encrypted
/openbmc/ipmitool/src/plugins/lanplus/
H A Dlanplus_crypt_impl.c143 * param input is the data to be encrypted
144 * param input_length is the number of bytes to be encrypted. This MUST
146 * param output is the encrypted output
290 lprintf(LOG_DEBUG, "Decrypted %d encrypted bytes", input_length); in lanplus_decrypt_aes_cbc_128()

1234567