Home
last modified time | relevance | path

Searched full:encryption (Results 1 – 25 of 1091) sorted by relevance

12345678910>>...44

/kernel/linux/linux-5.10/Documentation/x86/
Damd-memory-encryption.rst4 AMD Memory Encryption
7 Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV) are
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
[all …]
/kernel/linux/linux-4.19/Documentation/x86/
Damd-memory-encryption.txt1 Secure Memory Encryption (SME) and Secure Encrypted Virtualization (SEV) are
17 A page is encrypted when a page table entry has the encryption bit set (see
18 below on how to determine its position). The encryption bit can also be
20 successive level of page tables can also be encrypted by setting the encryption
23 encryption bit is set in cr3, doesn't imply the full hierarchy is encrypted.
24 Each page table entry in the hierarchy needs to have the encryption bit set to
25 achieve that. So, theoretically, you could have the encryption bit set in cr3
26 so that the PGD is encrypted, but not set the encryption bit in the PGD entry
32 memory. Since the memory encryption bit is controlled by the guest OS when it
34 forces the memory encryption bit to 1.
[all …]
/kernel/linux/linux-5.10/Documentation/block/
Dinline-encryption.rst4 Inline Encryption
10 Inline encryption hardware sits logically between memory and the disk, and can
11 en/decrypt data as it goes in/out of the disk. Inline encryption hardware has a
12 fixed number of "keyslots" - slots into which encryption contexts (i.e. the
13 encryption key, encryption algorithm, data unit size) can be programmed by the
15 of a keyslot (and also a data unit number to act as an encryption tweak), and
16 the inline encryption hardware will en/decrypt the data in the request with the
17 encryption context programmed into that keyslot. This is very different from
18 full disk encryption solutions like self encrypting drives/TCG OPAL/ATA
19 Security standards, since with inline encryption, any block on disk could be
[all …]
/kernel/linux/linux-5.10/Documentation/filesystems/
Dfscrypt.rst2 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
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
107 security vulnerability, can compromise all encryption keys that are
[all …]
/kernel/linux/linux-4.19/Documentation/filesystems/
Dfscrypt.rst2 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
83 After an encryption key has been provided, fscrypt is not designed to
88 Also note that as long as the encryption keys are *anywhere* in
99 some of the encryption keys as well. (Since Linux v4.12, all
116 encryption modes being used. For example, if AES-256-XTS is used for
[all …]
/kernel/linux/linux-4.19/include/linux/
Dfscrypt.h3 * fscrypt.h: declarations for per-file encryption
5 * Filesystems that implement per-file encryption include this header
7 * is being built with encryption support or not.
53 * fscrypt_require_key - require an inode's encryption key
56 * If the inode is encrypted, set up its encryption key if not already done.
63 * if a problem occurred while setting up the encryption key.
85 * encryption key is available --- since otherwise we'd have no way to encrypt
86 * the filename. Therefore, we first set up the directory's encryption key (if
90 * in an encrypted directory tree use the same encryption policy.
92 * Return: 0 on success, -ENOKEY if the directory's encryption key is missing,
[all …]
/kernel/linux/linux-5.10/arch/x86/mm/
Dmem_encrypt_boot.S3 * AMD Memory Encryption Support
26 * RCX - virtual address of the encryption workarea, including:
28 * - encryption routine page (PAGE_SIZE)
30 * R8 - physcial address of the pagetables to use for encryption
39 addq $PAGE_SIZE, %rax /* Workarea encryption routine */
46 /* Copy encryption routine into the workarea */
47 movq %rax, %rdi /* Workarea encryption routine */
48 leaq __enc_copy(%rip), %rsi /* Encryption routine */
49 movq $(.L__enc_copy_end - __enc_copy), %rcx /* Encryption routine length */
55 movq %r8, %rdx /* Pagetables used for encryption */
[all …]
/kernel/linux/linux-4.19/arch/x86/mm/
Dmem_encrypt_boot.S2 * AMD Memory Encryption Support
29 * RCX - virtual address of the encryption workarea, including:
31 * - encryption routine page (PAGE_SIZE)
33 * R8 - physcial address of the pagetables to use for encryption
42 addq $PAGE_SIZE, %rax /* Workarea encryption routine */
49 /* Copy encryption routine into the workarea */
50 movq %rax, %rdi /* Workarea encryption routine */
51 leaq __enc_copy(%rip), %rsi /* Encryption routine */
52 movq $(.L__enc_copy_end - __enc_copy), %rcx /* Encryption routine length */
58 movq %r8, %rdx /* Pagetables used for encryption */
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/
Ddm-crypt.rst5 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
139 For Authenticated Encryption with Additional Data (AEAD)
145 Use <bytes> as the encryption unit instead of 512 bytes sectors.
[all …]
/kernel/linux/linux-4.19/Documentation/device-mapper/
Ddm-crypt.txt4 Device-Mapper's "crypt" target provides transparent encryption of block devices
14 Encryption cipher, encryption mode and Initial Vector (IV) generator.
41 Key used for encryption. It is encoded either as a hexadecimal number
55 The encryption key size in bytes. The kernel key payload size must match
101 Perform encryption using the same cpu that IO was submitted on.
102 The default is to use an unbound workqueue so that encryption work
106 Disable offloading writes to a separate thread after encryption.
108 encryption threads to a single thread degrades performance
120 For Authenticated Encryption with Additional Data (AEAD)
126 Use <bytes> as the encryption unit instead of 512 bytes sectors.
[all …]
/kernel/linux/linux-4.19/fs/crypto/
Dcrypto.c2 * This contains encryption functions for per-file encryption.
9 * Filename encryption additions
11 * Encryption policy handling additions
61 * fscrypt_release_ctx() - Releases an encryption context
62 * @ctx: The encryption context to release.
64 * If the encryption context was allocated from the pre-allocated pool, returns
89 * fscrypt_get_ctx() - Gets an encryption context
93 * Allocates and initializes an encryption context.
95 * Return: An allocated and initialized encryption context on success; error
207 * @inode: The inode for which the encryption should take place
[all …]
Dfscrypt_private.h7 * This contains encryption key functions.
19 /* Encryption parameters */
24 * Encryption context for inode
28 * 1 byte: File contents encryption mode
29 * 1 byte: File names encryption mode
32 * 16 bytes: Encryption Key derivation nonce
/kernel/linux/linux-5.10/drivers/crypto/
Dsa2ul.h72 #define SA_ENG_ID_EM2 3 /* Encryption/Decryption enginefor pass 2 */
113 #define SA_CTX_ENC_TYPE1_SZ 64 /* Encryption SC with Key only */
114 #define SA_CTX_ENC_TYPE2_SZ 96 /* Encryption SC with Key and Aux1 */
126 * Bit 2-3: Fetch Encryption/Air Ciphering Bytes
227 * @submode: Encryption submodes
228 * @enc_size: Size of first pass encryption size
229 * @enc_size2: Size of second pass encryption size
230 * @enc_offset: Encryption payload offset in the packet
231 * @enc_iv: Encryption initialization vector for pass2
232 * @enc_iv2: Encryption initialization vector for pass2
[all …]
/kernel/linux/linux-5.10/fs/crypto/
Dpolicy.c3 * Encryption policy functions for per-file encryption support.
20 * fscrypt_policies_equal() - check whether two encryption policies are the same
93 * IV_INO_LBLK_* with other encryption modes arises. in supported_iv_ino_lblk_policy()
136 "Unsupported encryption modes (contents %d, filenames %d)", in fscrypt_supported_v1_policy()
144 fscrypt_warn(inode, "Unsupported encryption flags (0x%02x)", in fscrypt_supported_v1_policy()
172 "Unsupported encryption modes (contents %d, filenames %d)", in fscrypt_supported_v2_policy()
182 fscrypt_warn(inode, "Unsupported encryption flags (0x%02x)", in fscrypt_supported_v2_policy()
191 fscrypt_warn(inode, "Mutually exclusive encryption flags (0x%02x)", in fscrypt_supported_v2_policy()
218 fscrypt_warn(inode, "Reserved bits set in encryption policy"); in fscrypt_supported_v2_policy()
226 * fscrypt_supported_policy() - check whether an encryption policy is supported
[all …]
Dfscrypt_private.h51 * fscrypt_context - the encryption context of an inode
55 * fields from the fscrypt_policy, in order to identify the encryption algorithm
124 /* Return the contents encryption mode of a valid encryption policy */
137 /* Return the filenames encryption mode of a valid encryption policy */
150 /* Return the flags (FSCRYPT_POLICY_FLAG*) of a valid encryption policy */
173 * struct fscrypt_prepared_key - a key prepared for actual encryption/decryption
187 * fscrypt_info - the "encryption key" for an inode
195 /* The key in a form prepared for actual encryption/decryption */
203 * True if this inode will use inline encryption (blk-crypto) instead of
204 * the traditional filesystem-layer encryption.
[all …]
DKconfig3 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
32 Enable fscrypt to use inline encryption hardware if available.
Dinline_crypt.c3 * Inline encryption support for fscrypt
9 * With "inline encryption", the block layer handles the decryption/encryption
11 * crypto API. See Documentation/block/inline-encryption.rst. fscrypt still
66 /* Enable inline encryption for this file if supported. */
76 /* The file must need contents encryption, not filenames encryption */ in fscrypt_select_encryption_impl()
94 * IV_INO_LBLK_32 with blocksize != PAGE_SIZE from inline encryption. in fscrypt_select_encryption_impl()
235 * encryption, then assign the appropriate encryption context to the bio.
240 * The encryption context will be freed automatically when the bio is freed.
310 * encryption (or decryption) via fscrypt, filesystems should call this function
313 * bio because either the encryption key would be different or the encryption
Dhooks.c5 * Encryption hooks for higher-level filesystem operations.
17 * Currently, an encrypted regular file can only be opened if its encryption key
19 * Therefore, we first set up the inode's encryption key (if not already done)
24 * encryption policy. This is needed as part of the enforcement that all files
25 * in an encrypted directory tree use the same encryption policy, as a
45 "Inconsistent encryption context (parent directory: %lu)", in fscrypt_file_open()
148 * if the directory uses a v2 encryption policy. in fscrypt_prepare_setflags()
189 * -ENOKEY if the encryption key is missing, or another -errno code if a problem
190 * occurred while setting up the encryption key.
201 * the encryption policy which will be inherited from the directory. in fscrypt_prepare_symlink()
[all …]
/kernel/linux/linux-5.10/include/linux/
Dfscrypt.h3 * fscrypt.h: declarations for per-file encryption
5 * Filesystems that implement per-file encryption must include this header
88 * contents encryption
104 * as a result of the encryption key being added, DCACHE_NOKEY_NAME must be
120 * encryption key added yet. Such dentries may be either positive or negative.
129 * encryption key, but just checking for the key on the directory inode during
480 /* Encryption support disabled; use standard comparison */ in fscrypt_match_name()
643 * encryption
646 * Return: true if the inode requires file contents encryption and if the
647 * encryption should be done in the block layer via blk-crypto rather
[all …]
Dblk-crypto.h21 * struct blk_crypto_config - an inline encryption key's crypto configuration
22 * @crypto_mode: encryption algorithm this key is for
23 * @data_unit_size: the data unit size for all encryption/decryptions with this
36 * struct blk_crypto_key - an inline encryption key
58 * struct bio_crypt_ctx - an inline encryption context
117 * bio_crypt_clone - clone bio encryption context
122 * If @src has an encryption context, clone it to @dst.
/kernel/linux/linux-5.10/net/sunrpc/
DKconfig38 bool "Secure RPC: Disable insecure Kerberos encryption types"
42 Choose Y here to disable the use of deprecated encryption types
44 deprecated encryption types include DES-CBC-MD5, DES-CBC-CRC,
49 keytabs that contain only these deprecated encryption types.
50 Choosing Y prevents the use of known-insecure encryption types
/kernel/linux/linux-4.19/Documentation/crypto/
Ddescore-readme.txt4 des - fast & portable DES encryption & decryption.
30 1. Highest possible encryption/decryption PERFORMANCE.
50 30us per encryption (options: 64k tables, no IP/FP)
51 33us per encryption (options: 64k tables, FIPS standard bit ordering)
52 45us per encryption (options: 2k tables, no IP/FP)
53 48us per encryption (options: 2k tables, FIPS standard bit ordering)
55 this has the quickest encryption/decryption routines i've seen.
66 53us per encryption (uses 2k of tables)
70 encryption/decryption is still slower on the sparc and 68000.
84 68us per encryption (uses 2k of tables)
[all …]
/kernel/linux/linux-4.19/arch/x86/boot/compressed/
Dmem_encrypt.S2 * AMD Memory Encryption Support
44 * Pagetable bit position used to indicate encryption
57 andl $0x3f, %eax /* Return the encryption bit location */
81 call get_sev_encryption_bit /* Get the encryption bit position */
85 bts %rax, sme_me_mask(%rip) /* Create the encryption mask */
/kernel/linux/linux-5.10/Documentation/crypto/
Ddescore-readme.rst5 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 …]
/kernel/linux/linux-5.10/arch/x86/boot/compressed/
Dmem_encrypt.S3 * AMD Memory Encryption Support
35 * Pagetable bit position used to indicate encryption
48 andl $0x3f, %eax /* Return the encryption bit location */
75 call get_sev_encryption_bit /* Get the encryption bit position */
79 bts %rax, sme_me_mask(%rip) /* Create the encryption mask */

12345678910>>...44