/openbmc/linux/Documentation/block/ |
H A D | inline-encryption.rst | 12 Inline encryption hardware sits logically between memory and disk, and can 14 can control exactly how the inline encryption hardware will en/decrypt the data 18 Some inline encryption hardware accepts all encryption parameters including raw 19 keys directly in low-level I/O requests. However, most inline encryption 24 Note that inline encryption hardware is very different from traditional crypto 26 crypto accelerators operate on memory regions, whereas inline encryption 27 hardware operates on I/O requests. Thus, inline encryption hardware needs to be 30 Inline encryption hardware is also very different from "self-encrypting drives", 32 drives don't provide fine-grained control of encryption and provide no way to 33 verify the correctness of the resulting ciphertext. Inline encryption hardware [all …]
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | amd-memory-encryption.rst | 23 A page is encrypted when a page table entry has the encryption bit set (see 24 below on how to determine its position). The encryption bit can also be 26 successive level of page tables can also be encrypted by setting the encryption 29 encryption bit is set in cr3, doesn't imply the full hierarchy is encrypted. 30 Each page table entry in the hierarchy needs to have the encryption bit set to 31 achieve that. So, theoretically, you could have the encryption bit set in cr3 32 so that the PGD is encrypted, but not set the encryption bit in the PGD entry 38 memory. Since the memory encryption bit is controlled by the guest OS when it 40 forces the memory encryption bit to 1. 50 encryption [all …]
|
/openbmc/linux/Documentation/filesystems/ |
H A D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt) 9 transparent encryption of files and directories. 15 use encryption, see the documentation for the userspace tool `fscrypt 20 <https://source.android.com/security/encryption/file-based>`_, over 56 Provided that userspace chooses a strong encryption key, fscrypt 72 fscrypt (and storage encryption in general) can only provide limited 80 Cryptographic API algorithms or inline encryption hardware are. If a 89 After an encryption key has been added, fscrypt does not hide the 97 encryption but rather only by the correctness of the kernel. 98 Therefore, any encryption-specific access control checks would merely [all …]
|
/openbmc/qemu/qapi/ |
H A D | crypto.json | 68 # The supported algorithms for content encryption ciphers 110 # The supported modes for content encryption ciphers 129 # full disk encryption. The 'plain' generator should not be used for 137 # @essiv: 64-bit sector number encrypted with a hash of the encryption 148 # The supported full disk encryption formats 150 # @qcow: QCow/QCow2 built-in AES-CBC encryption. Use only for 153 # @luks: LUKS encryption format. Recommended for new images 163 # The common options that apply to all full disk encryption formats 165 # @format: the encryption format 175 # The options that apply to QCow/QCow2 AES-CBC encryption format [all …]
|
/openbmc/linux/fs/crypto/ |
H A D | Kconfig | 3 bool "FS Encryption (Per-file encryption)" 10 Enable encryption of files and directories. This 16 # Filesystems supporting encryption must select this if FS_ENCRYPTION. This 20 # Note: this option only pulls in the algorithms that filesystem encryption 21 # needs "by default". If userspace will use "non-default" encryption modes such 22 # as Adiantum encryption, then those other modes need to be explicitly enabled 46 Enable fscrypt to use inline encryption hardware if available.
|
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-protocols/opcua/ |
H A D | open62541_1.3.8.bb | 35 PACKAGECONFIG ?= "encryption-mbedtls pubsub pubsub-eth subscriptions subscriptions-events" 37 PACKAGECONFIG[encryption-mbedtls] = "-DUA_ENABLE_ENCRYPTION=MBEDTLS, , mbedtls, , , encryption-openssl" 38 PACKAGECONFIG[encryption-openssl] = "-DUA_ENABLE_ENCRYPTION=OPENSSL, , openssl, , , encryption-mbedtls"
|
/openbmc/qemu/tests/qemu-iotests/ |
H A D | 082.out | 58 encrypt.cipher-alg=<str> - Name of encryption cipher algorithm 59 encrypt.cipher-mode=<str> - Name of encryption cipher mode 61 encrypt.hash-alg=<str> - Name of encryption hash algorithm 66 …encryption=<bool (on/off)> - Encrypt the image with format 'aes'. (Deprecated in favor of encrypt.… 84 encrypt.cipher-alg=<str> - Name of encryption cipher algorithm 85 encrypt.cipher-mode=<str> - Name of encryption cipher mode 87 encrypt.hash-alg=<str> - Name of encryption hash algorithm 92 …encryption=<bool (on/off)> - Encrypt the image with format 'aes'. (Deprecated in favor of encrypt.… 110 encrypt.cipher-alg=<str> - Name of encryption cipher algorithm 111 encrypt.cipher-mode=<str> - Name of encryption cipher mode [all …]
|
H A D | 158.out | 3 Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=134217728 encryption=on 13 …MT', fmt=IMGFMT size=134217728 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT encryption=on
|
H A D | 087 | 139 _make_test_img --object secret,id=sec0,data=123456 -o encryption=on,encrypt.key-secret=sec0 $size 201 _make_test_img --object secret,id=sec0,data=123456 -o encryption=on,encrypt.key-secret=sec0 $size
|
H A D | 049 | 112 test_qemu_img create -f $IMGFMT -o encryption=off "$TEST_IMG" 64M 113 test_qemu_img create -f $IMGFMT --object secret,id=sec0,data=123456 -o encryption=on,encrypt.key-se…
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-crypt.rst | 5 Device-Mapper's "crypt" target provides transparent encryption of block devices 17 Encryption cipher, encryption mode and Initial Vector (IV) generator. 52 Key used for encryption. It is encoded either as a hexadecimal number 66 The encryption key size in bytes. The kernel key payload size must match 112 Perform encryption using the same cpu that IO was submitted on. 113 The default is to use an unbound workqueue so that encryption work 117 Disable offloading writes to a separate thread after encryption. 119 encryption threads to a single thread degrades performance 145 Use <bytes> as the encryption unit instead of 512 bytes sectors. 161 encryption with dm-crypt using the 'cryptsetup' utility, see [all …]
|
/openbmc/qemu/ |
H A D | qemu.sasl | 2 # pick a mechanism which provides session encryption as well 6 # you like for authentication, because TLS provides the encryption 8 # If you are only using UNIX sockets then encryption is not 21 # enable plugins which don't provide session encryption. The
|
/openbmc/linux/Documentation/virt/kvm/x86/ |
H A D | amd-memory-encryption.rst | 31 Bit[23] 1 = memory encryption can be enabled 32 0 = memory encryption can not be enabled 35 Bit[0] 1 = memory encryption can be enabled 36 0 = memory encryption can not be enabled 45 SEV hardware uses ASIDs to associate a memory encryption key with a VM. 100 The KVM_SEV_LAUNCH_START command is used for creating the memory encryption 101 context. To create the encryption context, user must provide a guest policy, 304 outgoing guest encryption context. 335 outgoing guest memory region with the encryption context creating using 363 issued by the hypervisor to delete the encryption context. [all …]
|
/openbmc/u-boot/board/xilinx/zynqmp/ |
H A D | Kconfig | 14 either authentication or encryption or both encryption
|
/openbmc/linux/drivers/crypto/aspeed/ |
H A D | Kconfig | 7 throughput of hash data digest, encryption and decryption. 47 Supports AES/DES symmetric-key encryption and decryption 58 Supports 256 bits to 4096 bits RSA encryption/decryption
|
/openbmc/u-boot/tools/ |
H A D | k3_x509template.txt | 21 # 1.3.6.1.4.1.294.1.4 = ASN1:SEQUENCE:encryption 38 # [ encryption ]
|
H A D | zynqimage.c | 74 uint32_t encryption; /* 0x28 */ member 99 checksum += le32_to_cpu(ptr->encryption); in zynqimage_checksum() 121 ptr->encryption = cpu_to_le32(ENCRYPTION_NONE); in zynqimage_default_header()
|
/openbmc/linux/Documentation/crypto/ |
H A D | descore-readme.rst | 5 Fast & Portable DES encryption & decryption 15 des - fast & portable DES encryption & decryption. 41 1. Highest possible encryption/decryption PERFORMANCE. 62 - 30us per encryption (options: 64k tables, no IP/FP) 63 - 33us per encryption (options: 64k tables, FIPS standard bit ordering) 64 - 45us per encryption (options: 2k tables, no IP/FP) 65 - 48us per encryption (options: 2k tables, FIPS standard bit ordering) 68 this has the quickest encryption/decryption routines i've seen. 80 - 53us per encryption (uses 2k of tables) 85 encryption/decryption is still slower on the sparc and 68000. [all …]
|
/openbmc/u-boot/board/xilinx/zynq/ |
H A D | Kconfig | 29 either authentication or encryption or both encryption
|
/openbmc/linux/net/sunrpc/ |
H A D | Kconfig | 45 Choose Y to enable the use of Kerberos 5 encryption types 51 bool "Enable Kerberos encryption types based on Camellia and CMAC" 57 Choose Y to enable the use of Kerberos 5 encryption types 70 Choose Y to enable the use of Kerberos 5 encryption types
|
/openbmc/linux/drivers/gpu/drm/amd/display/modules/hdcp/ |
H A D | hdcp1_transition.c | 81 } else if (!conn->is_repeater && input->encryption != PASS) { in mod_hdcp_hdcp1_transition() 131 input->encryption != PASS) { in mod_hdcp_hdcp1_transition() 229 } else if ((!conn->is_repeater && input->encryption != PASS) || in mod_hdcp_hdcp1_dp_transition() 308 } else if (input->encryption != PASS || in mod_hdcp_hdcp1_dp_transition()
|
/openbmc/openbmc/meta-security/recipes-security/fscryptctl/ |
H A D | fscryptctl_1.1.0.bb | 1 SUMMARY = "low-level tool handling Linux filesystem encryption" 3 policies for Linux filesystem encryption (https://lwn.net/Articles/639427). \
|
/openbmc/docs/designs/ |
H A D | estoraged.md | 28 Dm-crypt provides the encryption and device mapping capability, and Cryptsetup 44 - Volume key: The main encryption key used to encrypt the data on the block 102 object path. For example, this daemon would handle the encryption, whereas 112 encryption level. We will likely use the ioctl interface to send the relevant 117 but at the very least, encryption-only locking will be available, even if 121 used by eStoraged to generate two different passwords: the encryption password 150 And it provides several additional methods related to encryption: Lock, Unlock,
|
/openbmc/linux/Documentation/virt/kvm/s390/ |
H A D | s390-pv-dump.rst | 21 can be requested. The encryption is based on the Customer 50 metadata comprised of the encryption tweaks and status flags. The 52 time of the export does not matter as no re-encryption is
|
/openbmc/linux/crypto/ |
H A D | Kconfig | 373 solely on encryption (although decryption is supported as well, but 376 Instead of using 16 lookup tables of 1 KB each, (8 for encryption and 403 ARIA is a standard encryption algorithm of the Republic of Korea. 462 CAST6 (CAST-256) encryption algorithm (RFC2612) 505 national standard encryption algorithm of the Republic of Korea. 601 Adiantum tweakable, length-preserving encryption mode 603 Designed for fast and secure disk encryption, especially on 613 bound. Unlike XTS, Adiantum is a true wide-block encryption 688 for AES encryption. 703 HCTR2 length-preserving encryption mode [all …]
|