| /linux-6.15/Documentation/block/ |
| H A D | inline-encryption.rst | 18 Some inline encryption hardware accepts all encryption parameters including raw 42 encryption hardware is absent. We also want inline encryption to work with 95 encryption-related state for a particular inline encryption device. The 139 implement encryption in multiple ways. 275 Interaction between inline encryption and blk integrity 317 attack that storage encryption is intended to protect from. 402 key directly for inline encryption, but rather derives both an inline encryption 419 Inline encryption key Software secret 452 encryption key is used as the file contents encryption key, while the software 459 encryption optimized" settings, which use one file contents encryption key per [all …]
|
| H A D | index.rst | 16 inline-encryption
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | fscrypt.rst | 2 Filesystem-level encryption (fscrypt) 211 the key is used for v1 encryption policies or for v2 encryption 236 Per-file encryption keys 274 - For v1 encryption policies, the encryption is done directly with the 278 - For v2 encryption policies, the encryption is done with a per-mode 286 the encryption keys are derived from the master key, encryption mode 450 Contents encryption 510 Filenames encryption 711 had encryption enabled on it. (For example, to use encryption on an 939 For v1 encryption policies, a master encryption key can also be [all …]
|
| H A D | ubifs-authentication.rst | 20 At the current state, UBIFS encryption however does not prevent attacks where 28 Other full disk encryption systems like dm-crypt cover all filesystem metadata, 38 name encryption, the authentication system could be tied into fscrypt such that 40 be possible to use UBIFS authentication without using encryption. 395 (fscrypt) to provide confidentiality and authenticity. Since UBIFS encryption 396 has a different approach of encryption policies per directory, there can be 397 multiple fscrypt master keys and there might be folders without encryption. 401 encryption, it does not share the same master key with fscrypt, but manages 411 or key in userspace that covers UBIFS authentication and encryption. This can 414 encryption. [all …]
|
| /linux-6.15/fs/crypto/ |
| H A D | Kconfig | 3 bool "FS Encryption (Per-file encryption)" 11 Enable encryption of files and directories. This 17 # Filesystems supporting encryption must select this if FS_ENCRYPTION. This 21 # Note: this option only pulls in the algorithms that filesystem encryption 22 # needs "by default". If userspace will use "non-default" encryption modes such 23 # as Adiantum encryption, then those other modes need to be explicitly enabled 43 Enable fscrypt to use inline encryption hardware if available.
|
| /linux-6.15/Documentation/arch/x86/ |
| H A D | amd-memory-encryption.rst | 24 below on how to determine its position). The encryption bit can also be 40 forces the memory encryption bit to 1. 50 encryption 52 memory encryption is enabled (this only affects 57 determine if SME is enabled and/or to enable memory encryption:: 60 Bit[23] 0 = memory encryption features are disabled 61 1 = memory encryption features are enabled 67 Bit[0] 0 = memory encryption is not active 68 1 = memory encryption is active 86 the encryption bit to page table entries (the SME mask in the [all …]
|
| H A D | index.rst | 28 amd-memory-encryption
|
| /linux-6.15/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 122 Disable offloading writes to a separate thread after encryption. 124 encryption threads to a single thread degrades performance 155 Use <bytes> as the encryption unit instead of 512 bytes sectors. 192 encryption with dm-crypt using the 'cryptsetup' utility, see [all …]
|
| /linux-6.15/drivers/crypto/aspeed/ |
| H A D | Kconfig | 7 throughput of hash data digest, encryption and decryption. 45 Supports AES/DES symmetric-key encryption and decryption 56 Supports 256 bits to 4096 bits RSA encryption/decryption
|
| /linux-6.15/Documentation/crypto/ |
| H A D | krb5.rst | 24 This API provides Kerberos 5-style cryptography for key derivation, encryption 83 type for encryption and checksumming respectively. They hold 93 encryption mode. 97 * ``block_len``, ``conf_len`` and ``cksum_len`` are the encryption block 99 used in encryption mode, but only the checksum length is used in checksum 109 Once the application has selected an encryption type, the keys that will be 150 (checksum-only or full encryption). 186 crypto object, an AEAD template for encryption and a synchronous hash for 209 For the encryption function, the output buffer may be larger than is needed
|
| 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) 80 - 53us per encryption (uses 2k of tables) 106 - 68us per encryption (uses 2k of tables) 133 - 108us per encryption (uses 34k worth of tables) 153 - 165us per encryption (uses 6k worth of tables) 162 - 226us per encryption 387 e.g., encryption filters, etc. [all …]
|
| H A D | api-samples.rst | 8 all inputs are random bytes, the encryption is done in-place, and it's 29 * encryption/decryption operations. But in this example, we'll just do a 30 * single encryption operation with it (which is not very efficient).
|
| H A D | userspace-if.rst | 95 to provide different memory pointers for the encryption and decryption 159 should be processed for encryption or decryption. In addition, the IV is 170 - ALG_OP_ENCRYPT - encryption of data 218 should be processed for encryption or decryption. In addition, the IV is 229 - ALG_OP_ENCRYPT - encryption of data 277 - AEAD encryption input: AAD \|\| plaintext 284 - AEAD encryption output: ciphertext \|\| authentication tag 388 key for symmetric encryption. 395 AEAD ciphers. For a encryption operation, the authentication tag of
|
| /linux-6.15/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. 132 The KVM_SEV_LAUNCH_START command is used for creating the memory encryption 336 outgoing guest encryption context. 367 outgoing guest memory region with the encryption context creating using 395 issued by the hypervisor to delete the encryption context. 441 the incoming buffers into the guest memory region with encryption context [all …]
|
| H A D | index.rst | 10 amd-memory-encryption
|
| /linux-6.15/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
|
| /linux-6.15/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()
|
| H A D | hdcp1_execution.c | 236 &input->encryption, &status, in computations_validate_rx_test_for_repeater() 241 &input->encryption, &status, in computations_validate_rx_test_for_repeater() 362 if (input->encryption != PASS) in read_ksv_list() 364 &input->encryption, &status, in read_ksv_list()
|
| /linux-6.15/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
|
| /linux-6.15/crypto/ |
| H A D | Kconfig | 465 CAST6 (CAST-256) encryption algorithm (RFC2612) 604 Adiantum tweakable, length-preserving encryption mode 606 Designed for fast and secure disk encryption, especially on 616 bound. Unlike XTS, Adiantum is a true wide-block encryption 683 for AES encryption. 698 HCTR2 length-preserving encryption mode 802 authenticated encryption mode (NIST SP800-38C) 841 This IV generator generates an IV based on the encryption of 852 dm-crypt. It uses the hash of the block encryption key as the 855 encryption. [all …]
|
| /linux-6.15/net/tipc/ |
| H A D | Kconfig | 40 bool "TIPC encryption support" 47 Saying Y here will enable support for TIPC encryption.
|
| /linux-6.15/arch/arm/crypto/ |
| H A D | Kconfig | 186 and for XTS mode encryption, CBC and XTS mode decryption speedup is 187 around 25%. (CBC encryption speed is not affected by this driver.) 194 encryption (not CBC decryption), the encryption of XTS tweaks, XTS
|
| /linux-6.15/block/ |
| H A D | Kconfig | 196 bool "Enable inline encryption support in block layer" 199 block layer handle encryption, so users can take 200 advantage of inline encryption hardware if present. 208 Enabling this lets the block layer handle inline encryption 210 encryption hardware is not present.
|
| /linux-6.15/drivers/crypto/intel/qat/qat_common/ |
| H A D | qat_crypto.h | 49 bool encryption; member
|
| /linux-6.15/drivers/net/wireless/purelifi/plfxlc/ |
| H A D | Kconfig | 9 The driver supports common 802.11 encryption/authentication
|