| /openbmc/linux/tools/perf/pmu-events/arch/s390/cf_z16/ |
| H A D | pai_crypto.json | 34 "BriefDescription": "KM ENCRYPTED DEA",
35 "PublicDescription": "KM-Encrypted-DEA function ending with CC=0"
41 "BriefDescription": "KM ENCRYPTED TDEA 128",
42 "PublicDescription": "KM-Encrypted-TDEA-128 function ending with CC=0"
48 "BriefDescription": "KM ENCRYPTED TDEA 192",
49 "PublicDescription": "KM-Encrypted-TDEA-192 function ending with CC=0"
76 "BriefDescription": "KM ENCRYPTED AES 128",
77 "PublicDescription": "KM-Encrypted-AES-128 function ending with CC=0"
83 "BriefDescription": "KM ENCRYPTED AES 192",
84 "PublicDescription": "KM-Encrypted-AES-192 function ending with CC=0"
[all …]
|
| /openbmc/linux/Documentation/security/keys/ |
| H A D | ecryptfs.rst | 2 Encrypted keys for the eCryptfs filesystem
8 Each FEK is in turn encrypted with a File Encryption Key Encryption Key (FEKEK)
12 the FEK is encrypted by 'ecryptfsd' with the help of external libraries in order
22 The 'encrypted' key type has been extended with the introduction of the new
24 filesystem. Encrypted keys of the newly introduced format store an
31 encrypted form.
33 The eCryptfs filesystem may really benefit from using encrypted keys in that the
42 keyctl add encrypted name "new ecryptfs key-type:master-key-name keylen" ring
43 keyctl add encrypted name "load hex_blob" ring
53 Example of encrypted key usage with the eCryptfs filesystem:
[all …]
|
| H A D | trusted-encrypted.rst | 2 Trusted and Encrypted Keys
5 Trusted and Encrypted Keys are two new key types added to the existing kernel
8 stores, and loads only encrypted blobs. Trusted Keys require the availability
9 of a Trust Source for greater security, while Encrypted Keys can be used on any
109 New keys are created from random numbers. They are encrypted/decrypted using
135 Encrypted Keys
138 Encrypted keys do not depend on a trust source, and are faster, as they use AES
140 random numbers or user-provided decrypted data, and are encrypted/decrypted
142 user-key type. The main disadvantage of encrypted keys is that if they are not
234 Encrypted Keys usage
[all …]
|
| /openbmc/qemu/target/s390x/ |
| H A D | cpu_features_def.h.inc | 194 DEF_FEAT(KMAC_EDEA, "kmac-edea", KMAC, 9, "KMAC Encrypted-DEA")
195 DEF_FEAT(KMAC_ETDEA_128, "kmac-etdea-128", KMAC, 10, "KMAC Encrypted-TDEA-128")
196 DEF_FEAT(KMAC_ETDEA_192, "kmac-etdea-192", KMAC, 11, "KMAC Encrypted-TDEA-192")
200 DEF_FEAT(KMAC_EAES_128, "kmac-eaes-128", KMAC, 26, "KMAC Encrypted-AES-128")
201 DEF_FEAT(KMAC_EAES_192, "kmac-eaes-192", KMAC, 27, "KMAC Encrypted-AES-192")
202 DEF_FEAT(KMAC_EAES_256, "kmac-eaes-256", KMAC, 28, "KMAC Encrypted-AES-256")
208 DEF_FEAT(KMC_EDEA, "kmc-edea", KMC, 9, "KMC Encrypted-DEA")
209 DEF_FEAT(KMC_ETDEA_128, "kmc-etdea-128", KMC, 10, "KMC Encrypted-TDEA-128")
210 DEF_FEAT(KMC_ETDEA_192, "kmc-etdea-192", KMC, 11, "KMC Encrypted-TDEA-192")
214 DEF_FEAT(KMC_EAES_128, "kmc-eaes-128", KMC, 26, "KMC Encrypted-AES-128")
[all …]
|
| /openbmc/linux/arch/x86/mm/ |
| H A D | mem_encrypt_boot.S | 23 * RDI - virtual address for the encrypted mapping
36 /* Set up a one page stack in the non-encrypted memory area */
42 movq %rdi, %r10 /* Encrypted area */
53 movq %r10, %rdi /* Encrypted area */
78 * the kernel will be encrypted during the process. So this
84 * RDI - virtual address for the encrypted mapping
92 * The area will be encrypted by copying from the non-encrypted
94 * intermediate buffer back to the encrypted memory space. The physical
96 * being encrypted "in place".
112 movq %rdi, %r10 /* Save encrypted area address */
[all …]
|
| /openbmc/u-boot/doc/imx/habv4/guides/ |
| H A D | encrypted_boot.txt | 1 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/linux/Documentation/filesystems/ |
| H A D | fscrypt.rst | 35 UBIFS. This allows encrypted files to be read and written without
36 caching both the decrypted and encrypted pages in the pagecache,
39 needed. eCryptfs also limits encrypted filenames to 143 bytes,
45 supports marking an empty directory as encrypted. Then, after
48 encrypted.
118 "locked", i.e. in ciphertext or encrypted form.
124 encrypted files and directories before removing a master key, as
126 encrypted directory.
156 with another user's encrypted files to which they have read-only
169 policies on all new encrypted directories.
[all …]
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | amd-memory-encryption.rst | 7 Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV) are
10 SME provides the ability to mark individual pages of memory as encrypted using
11 the standard x86 page tables. A page that is marked encrypted will be
12 automatically decrypted when read from DRAM and encrypted when written to
16 SEV enables running encrypted virtual machines (VMs) in which the code and data
19 memory. Private memory is encrypted with the guest-specific key, while shared
20 memory may be encrypted with hypervisor key. When SME is enabled, the hypervisor
23 A page is encrypted when a page table entry has the encryption bit set (see
25 specified in the cr3 register, allowing the PGD table to be encrypted. Each
26 successive level of page tables can also be encrypted by setting the encryption
[all …]
|
| /openbmc/linux/fs/crypto/ |
| H A D | hooks.c | 11 * fscrypt_file_open() - prepare to open a possibly-encrypted regular file
15 * Currently, an encrypted regular file can only be opened if its encryption key
16 * is available; access to the raw encrypted contents is not supported.
21 * is being opened) is encrypted, then the inode being opened uses the same
23 * in an encrypted directory tree use the same encryption policy, as a
26 * an unencrypted file in an encrypted directory.
116 * @dir: the encrypted directory being searched
177 * When the CASEFOLD flag is set on an encrypted directory, we must in fscrypt_prepare_setflags()
201 * fscrypt_prepare_symlink() - prepare to create a possibly-encrypted symlink
210 * encrypted symlink may be longer than the original.
[all …]
|
| /openbmc/linux/security/keys/encrypted-keys/ |
| H A D | Makefile | 3 # Makefile for encrypted keys
6 obj-$(CONFIG_ENCRYPTED_KEYS) += encrypted-keys.o
8 encrypted-keys-y := encrypted.o ecryptfs_format.o
11 encrypted-keys-y += $(masterkey-y) $(masterkey-m-m)
|
| H A D | masterkey_trusted.c | 11 * See Documentation/security/keys/trusted-encrypted.rst
17 #include <keys/encrypted-type.h>
18 #include "encrypted.h"
24 * manages both trusted/encrypted key-types, like the encrypted key type
|
| H A D | encrypted.c | 11 * See Documentation/security/keys/trusted-encrypted.rst
23 #include <keys/encrypted-type.h>
35 #include "encrypted.h"
84 "Allow instantiation of encrypted keys using provided decrypted data");
103 * valid_ecryptfs_desc - verify the description of a new/loaded encrypted key
105 * The description of a encrypted key with format 'ecryptfs' must contain
168 * <encrypted iv + data>
294 /* convert the hex encoded iv, encrypted-data and HMAC to ascii */ in datablob_format()
305 * Use a user provided key to encrypt/decrypt an encrypted-key.
515 /* verify HMAC before decrypting encrypted key */
[all …]
|
| /openbmc/openbmc/meta-arm/meta-arm-systemready/recipes-test/arm-systemready-linux-distros/files/unattended-boot-conf/openSUSE/ |
| H A D | autoinst.xml | 592 <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/docs/designs/ |
| H A D | estoraged.md | 1 # eStoraged Design - Encrypted Secondary Storage Management Daemon
12 This daemon will serve as an abstraction for an encrypted storage device,
14 manage the encrypted filesystem on the device. Using the D-Bus interface, other
16 encrypted filesystem, wipe its contents, lock/unlock the device, or change the
54 - Create a new LUKS encrypted filesystem on the device
73 client daemon on the BMC will interact with eStoraged to set up a new encrypted
105 To manage the encrypted filesystem, we will make use of the
131 encrypted filesystem), the D-Bus interface will be asynchronous, with the
140 is often used to unlock an encrypted block device, where it takes the password
147 for each storage device in a system. It is capable of setting up an encrypted
[all …]
|
| /openbmc/phosphor-net-ipmid/ |
| H A D | crypt_algo.hpp | 18 * 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/qemu/docs/system/i386/ |
| H A D | amd-memory-encryption.rst | 1 AMD Secure Encrypted Virtualization (SEV)
4 Secure Encrypted Virtualization (SEV) is a feature found on AMD processors.
6 SEV is an extension to the AMD-V architecture which supports running encrypted
7 virtual machines (VMs) under the control of KVM. Encrypted VMs have their pages
9 unencrypted version. Each encrypted VM is associated with a unique encryption
11 encrypted guests data will be incorrectly decrypted, leading to unintelligible
18 encrypted guest. These SEV commands can be issued via KVM_MEMORY_ENCRYPT_OP
21 Secure Encrypted Virtualization - Encrypted State (SEV-ES) builds on the SEV
31 Boot images (such as bios) must be encrypted before a guest can be booted. The
82 ``LAUNCH_MEASURE`` can be used to retrieve the measurement of encrypted memory and,
[all …]
|
| /openbmc/linux/security/keys/ |
| H A D | Kconfig | 78 Userspace will only ever see encrypted blobs.
87 tristate "ENCRYPTED KEYS"
97 in the kernel. Encrypted keys are instantiated using kernel
99 encrypted/decrypted with a 'master' symmetric key. The 'master'
100 key can be either a trusted-key or user-key type. Only encrypted
106 bool "Allow encrypted keys with user decrypted data"
109 This option provides support for instantiating encrypted keys using
|
| /openbmc/linux/Documentation/driver-api/nvdimm/ |
| H A D | security.rst | 51 A nvdimm encrypted-key of format enc32 has the description format of:
54 See file ``Documentation/security/keys/trusted-encrypted.rst`` for creating
55 encrypted-keys of enc32 format. TPM usage with a master trusted key is
56 preferred for sealing the encrypted-keys.
64 relevant encrypted-keys into the kernel user keyring during the initramfs phase.
115 An encrypted-key with the current user passphrase that is tied to the nvdimm
125 is just another encrypted-key.
136 another encrypted-key.
|
| /openbmc/linux/Documentation/virt/kvm/s390/ |
| H A D | s390-pv-boot.rst | 12 Memory made accessible to the hypervisor will be encrypted. See
16 information about the encrypted components and necessary metadata to
27 switch into PV mode itself, the user can load encrypted guest
59 The components are for instance an encrypted kernel, kernel parameters
62 After the initial import of the encrypted data, all defined pages will
82 encrypted images.
|
| H A D | s390-pv-dump.rst | 20 provides an interface to KVM over which encrypted CPU and memory data
34 and extracts dump keys with which the VM dump data will be encrypted.
46 write out the encrypted vcpu state, but also the unencrypted state
49 The memory state is further divided into the encrypted memory and its
51 encrypted memory can simply be read once it has been exported. The
|
| /openbmc/linux/net/tls/ |
| H A D | trace.h | 47 bool encrypted, bool decrypted),
49 TP_ARGS(sk, tcp_seq, rec_no, rec_len, encrypted, decrypted),
56 __field( bool, encrypted )
65 __entry->encrypted = encrypted;
70 "sk=%p tcp_seq=%u rec_no=%llu len=%u encrypted=%d decrypted=%d",
73 __entry->encrypted, __entry->decrypted
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 191.out | 145 "encrypted": false,
173 "encrypted": false,
214 "encrypted": false,
242 "encrypted": false,
283 "encrypted": false,
311 "encrypted": false,
340 "encrypted": false,
368 "encrypted": false,
552 "encrypted": false,
580 "encrypted": false,
[all …]
|
| /openbmc/linux/arch/x86/crypto/ |
| H A D | cast5-avx-x86_64-asm_64.S | 227 * RL1: encrypted blocks 1 and 2
228 * RR1: encrypted blocks 3 and 4
229 * RL2: encrypted blocks 5 and 6
230 * RR2: encrypted blocks 7 and 8
231 * RL3: encrypted blocks 9 and 10
232 * RR3: encrypted blocks 11 and 12
233 * RL4: encrypted blocks 13 and 14
234 * RR4: encrypted blocks 15 and 16
291 * RL1: encrypted blocks 1 and 2
292 * RR1: encrypted blocks 3 and 4
[all …]
|
| /openbmc/linux/Documentation/process/ |
| H A D | embargoed-hardware-issues.rst | 38 The list is encrypted and email to the list can be sent by either PGP or
39 S/MIME encrypted and must be signed with the reporter's PGP key or S/MIME
62 The encrypted mailing-lists which are used in our process are hosted on
120 other factors and should be only used when absolutely necessary. Encrypted
133 The hardware security team will provide an incident-specific encrypted
170 team via the specific encrypted mailing-list.
179 The initial response team sets up an encrypted mailing-list or repurposes
281 Encrypted mailing-lists
284 We use encrypted mailing-lists for communication. The operating principle
285 of these lists is that email sent to the list is encrypted either with the
[all …]
|
| /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
|