| /openbmc/estoraged/ |
| H A D | README.md | 3 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/u-boot/doc/imx/habv4/guides/ |
| H A D | encrypted_boot.txt | 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/tests/qemu-iotests/ |
| H A D | 191.out | 146 "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 D | 273.out | 65 "encrypted": false,
94 "encrypted": false,
135 "encrypted": false,
164 "encrypted": false,
193 "encrypted": false,
|
| H A D | 210.out | 18 encrypted: yes
71 encrypted: yes
127 encrypted: yes
198 encrypted: yes
|
| H A D | 184.out | 56 "encrypted": false,
86 "encrypted": false,
|
| /openbmc/qemu/tests/qemu-iotests/tests/ |
| H A D | qcow2-encryption.out | 3 === Create an encrypted image ===
19 encrypted: yes
|
| /openbmc/u-boot/board/xilinx/zynq/ |
| H A D | Kconfig | 14 bool "Enable zynq aes command for decryption of encrypted images"
18 Decrypts the encrypted image present in source address
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/polkit/files/ |
| H A D | 50-org.freedesktop.udiskie.rules | 11 "org.freedesktop.udisks2.encrypted-unlock": YES,
17 "org.freedesktop.udisks2.encrypted-unlock-other-seat": YES,
|
| /openbmc/docs/designs/ |
| H A D | estoraged.md | 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
|
| /openbmc/qemu/docs/specs/ |
| H A D | ppc-spapr-uv-hcalls.rst | 32 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/qemu/docs/system/i386/ |
| H A D | amd-memory-encryption.rst | 8 SEV is an extension to the AMD-V architecture which supports running encrypted
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
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,
85 for a SEV-ES guest, encrypted VMSAs. This measurement is a signature of the
87 to the guest owner as an attestation that the memory and VMSAs were encrypted
113 guest register state is encrypted and cannot be updated by the VMM/hypervisor,
168 Boot images (such as bios) must be encrypted before a guest can be booted. The
[all …]
|
| /openbmc/qemu/docs/system/s390x/ |
| H A D | protvirt.rst | 5 (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/estoraged/service_files/ |
| H A D | xyz.openbmc_project.eStoraged.service.in | 2 Description=Storage management daemon for an encrypted storage device
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-eth-keyfile_0.8.0.bb | 1 SUMMARY = "A library for handling the encrypted keyfiles used to store ethereum private keys."
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/storage/ |
| H A D | estoraged_git.bb | 2 DESCRIPTION = "Provides a D-Bus interface to manage an encrypted storage device"
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-core/systemd/ |
| H A D | systemd_%.bbappend | 3 # for encrypted filesystems
|
| /openbmc/u-boot/doc/imx/habv4/ |
| H A D | introduction_habv4.txt | 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] .
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm1/openssl-tpm-engine/files/ |
| H A D | 0003-tpm-openssl-tpm-engine-parse-an-encrypted-tpm-SRK-pa.patch | 4 Subject: [PATCH] tpm:openssl-tpm-engine:parse an encrypted tpm SRK password
9 So, we improve it and support to get an encrypted (AES algorithm)
16 "xxxxxxxx" is the encrypted SRK password for libtpm.so.
|
| /openbmc/openbmc/poky/meta/recipes-extended/unzip/unzip/ |
| H A D | CVE-2015-7696.patch | 20 GLOBAL(pInfo->encrypted) = FALSE;
|
| /openbmc/openbmc/meta-security/recipes-security/cryptmount/ |
| H A D | cryptmount_6.2.0.bb | 1 SUMMARY = "Linux encrypted filesystem management tool"
|
| /openbmc/openbmc/poky/meta/recipes-core/busybox/busybox/ |
| H A D | 0001-testsuite-check-uudecode-before-using-it.patch | 37 # File containing some damaged encrypted stream
|
| /openbmc/docs/architecture/ |
| H A D | user-management.md | 22 pam-unix), which will store the password in encrypted form. Implementation
94 …| pam_unix - | pam_ipmi- encrypted| | | || channel …
199 password in encrypted form, if | | …
247 … | |encrypted form along with |
287 … | | encrypted password. |
361 encrypted form, which will be used by IPMI. The same has been performed by
396 | | password in encrypted form | |
488 user requires clear text password to be stored in encrypted form. Similarly
|
| /openbmc/openbmc/meta-security/recipes-security/fscrypt/ |
| H A D | fscrypt_1.1.0.bb | 3 and provides a uniform interface for creating and modifying encrypted directories. For \
|
| /openbmc/qemu/docs/system/ |
| H A D | secrets.rst | 110 The ``BASE64-IV`` data is 16 random bytes which have been base64 encrypted.
147 then pass all subsequent inline secrets encrypted with the master key.
156 The secrets for individual QEMU device backends must all then be encrypted
|