Searched refs:encryption (Results 1 – 25 of 123) sorted by relevance
12345
12 Inline encryption hardware sits logically between memory and disk, and can14 can control exactly how the inline encryption hardware will en/decrypt the data18 Some inline encryption hardware accepts all encryption parameters including raw19 keys directly in low-level I/O requests. However, most inline encryption24 Note that inline encryption hardware is very different from traditional crypto26 crypto accelerators operate on memory regions, whereas inline encryption27 hardware operates on I/O requests. Thus, inline encryption hardware needs to be30 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 to33 verify the correctness of the resulting ciphertext. Inline encryption hardware[all …]
16 inline-encryption
23 A page is encrypted when a page table entry has the encryption bit set (see24 below on how to determine its position). The encryption bit can also be26 successive level of page tables can also be encrypted by setting the encryption29 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 to31 achieve that. So, theoretically, you could have the encryption bit set in cr332 so that the PGD is encrypted, but not set the encryption bit in the PGD entry38 memory. Since the memory encryption bit is controlled by the guest OS when it40 forces the memory encryption bit to 1.50 encryption[all …]
28 amd-memory-encryption
2 Filesystem-level encryption (fscrypt)9 transparent encryption of files and directories.15 use encryption, see the documentation for the userspace tool `fscrypt20 <https://source.android.com/security/encryption/file-based>`_, over56 Provided that userspace chooses a strong encryption key, fscrypt72 fscrypt (and storage encryption in general) can only provide limited80 Cryptographic API algorithms or inline encryption hardware are. If a89 After an encryption key has been added, fscrypt does not hide the97 encryption but rather only by the correctness of the kernel.98 Therefore, any encryption-specific access control checks would merely[all …]
20 At the current state, UBIFS encryption however does not prevent attacks where28 Other full disk encryption systems like dm-crypt cover all filesystem metadata,38 name encryption, the authentication system could be tied into fscrypt such that40 be possible to use UBIFS authentication without using encryption.394 UBIFS authentication is intended to operate side-by-side with UBIFS encryption395 (fscrypt) to provide confidentiality and authenticity. Since UBIFS encryption396 has a different approach of encryption policies per directory, there can be397 multiple fscrypt master keys and there might be folders without encryption.401 encryption, it does not share the same master key with fscrypt, but manages411 or key in userspace that covers UBIFS authentication and encryption. This can[all …]
3 bool "FS Encryption (Per-file encryption)"10 Enable encryption of files and directories. This16 # Filesystems supporting encryption must select this if FS_ENCRYPTION. This20 # Note: this option only pulls in the algorithms that filesystem encryption21 # needs "by default". If userspace will use "non-default" encryption modes such22 # as Adiantum encryption, then those other modes need to be explicitly enabled46 Enable fscrypt to use inline encryption hardware if available.
5 Device-Mapper's "crypt" target provides transparent encryption of block devices17 Encryption cipher, encryption mode and Initial Vector (IV) generator.52 Key used for encryption. It is encoded either as a hexadecimal number66 The encryption key size in bytes. The kernel key payload size must match112 Perform encryption using the same cpu that IO was submitted on.113 The default is to use an unbound workqueue so that encryption work117 Disable offloading writes to a separate thread after encryption.119 encryption threads to a single thread degrades performance145 Use <bytes> as the encryption unit instead of 512 bytes sectors.161 encryption with dm-crypt using the 'cryptsetup' utility, see[all …]
31 Bit[23] 1 = memory encryption can be enabled32 0 = memory encryption can not be enabled35 Bit[0] 1 = memory encryption can be enabled36 0 = memory encryption can not be enabled45 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 encryption101 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 using363 issued by the hypervisor to delete the encryption context.[all …]
10 amd-memory-encryption
7 throughput of hash data digest, encryption and decryption.47 Supports AES/DES symmetric-key encryption and decryption58 Supports 256 bits to 4096 bits RSA encryption/decryption
5 Fast & Portable DES encryption & decryption15 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 …]
8 all inputs are random bytes, the encryption is done in-place, and it's29 * encryption/decryption operations. But in this example, we'll just do a30 * single encryption operation with it (which is not very efficient).
95 to provide different memory pointers for the encryption and decryption159 should be processed for encryption or decryption. In addition, the IV is170 - ALG_OP_ENCRYPT - encryption of data218 should be processed for encryption or decryption. In addition, the IV is229 - ALG_OP_ENCRYPT - encryption of data277 - AEAD encryption input: AAD \|\| plaintext284 - AEAD encryption output: ciphertext \|\| authentication tag388 key for symmetric encryption.395 AEAD ciphers. For a encryption operation, the authentication tag of
45 Choose Y to enable the use of Kerberos 5 encryption types51 bool "Enable Kerberos encryption types based on Camellia and CMAC"57 Choose Y to enable the use of Kerberos 5 encryption types70 Choose Y to enable the use of Kerberos 5 encryption types
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()
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()
21 can be requested. The encryption is based on the Customer50 metadata comprised of the encryption tweaks and status flags. The52 time of the export does not matter as no re-encryption is
373 solely on encryption (although decryption is supported as well, but376 Instead of using 16 lookup tables of 1 KB each, (8 for encryption and403 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 mode603 Designed for fast and secure disk encryption, especially on613 bound. Unlike XTS, Adiantum is a true wide-block encryption688 for AES encryption.703 HCTR2 length-preserving encryption mode[all …]
195 bool "Enable inline encryption support in block layer"198 block layer handle encryption, so users can take199 advantage of inline encryption hardware if present.207 Enabling this lets the block layer handle inline encryption209 encryption hardware is not present.
40 bool "TIPC encryption support"46 Saying Y here will enable support for TIPC encryption.
27 - with or without encryption) as well as card before the Cisco50 - with or without encryption) as well as card before the Cisco
49 bool encryption; member
9 The driver supports common 802.11 encryption/authentication
51 UCHAR encryption; member
