Filesystem Crypto
[Prev Page][Next Page]
- Re: [PATCH 09/13] fscrypt: support decrypting multiple filesystem blocks per page
- Re: [PATCH 07/13] fscrypt: handle blocksize < PAGE_SIZE in fscrypt_zeroout_range()
- Re: [PATCH 05/13] fscrypt: introduce fscrypt_encrypt_block_inplace()
- Re: [PATCH 03/13] fscrypt: rename fscrypt_do_page_crypto() to fscrypt_crypt_block()
- Re: [f2fs-dev] [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- Re: [PATCH 02/13] fscrypt: remove the "write" part of struct fscrypt_ctx
- Re: [PATCH 01/13] fscrypt: simplify bounce page handling
- Re: [f2fs-dev] [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- [PATCH 01/13] fscrypt: simplify bounce page handling
- [PATCH 04/13] fscrypt: clean up some BUG_ON()s in block encryption/decryption
- [PATCH 05/13] fscrypt: introduce fscrypt_encrypt_block_inplace()
- [PATCH 03/13] fscrypt: rename fscrypt_do_page_crypto() to fscrypt_crypt_block()
- [PATCH 07/13] fscrypt: handle blocksize < PAGE_SIZE in fscrypt_zeroout_range()
- [PATCH 10/13] ext4: clear BH_Uptodate flag on decryption error
- [PATCH 06/13] fscrypt: support encrypting multiple filesystem blocks per page
- [PATCH 12/13] ext4: decrypt only the needed block in __ext4_block_zero_page_range()
- [PATCH 13/13] ext4: encrypt only up to last block in ext4_bio_write_page()
- [PATCH 09/13] fscrypt: support decrypting multiple filesystem blocks per page
- [PATCH 11/13] ext4: decrypt only the needed blocks in ext4_block_write_begin()
- [PATCH 08/13] fscrypt: introduce fscrypt_decrypt_block_inplace()
- [PATCH 02/13] fscrypt: remove the "write" part of struct fscrypt_ctx
- [PATCH 00/13] fscrypt, ext4: prepare for blocksize != PAGE_SIZE
- Re: [f2fs-dev] [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- Re: [f2fs-dev] [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- Re: [PATCH V2 11/13] ext4: Compute logical block and the page range to be encrypted
- Re: [PATCH V2 07/13] Add decryption support for sub-pagesized blocks
- Re: [PATCH V2 03/13] fsverity: Add call back to decide if verity check has to be performed
- Re: [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- Re: [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- Re: [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- Re: [PATCH V2 12/13] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- Re: [f2fs-dev] [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- Re: [PATCH V2 03/13] fsverity: Add call back to decide if verity check has to be performed
- Re: [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- Re: [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- Re: [PATCH V2 11/13] ext4: Compute logical block and the page range to be encrypted
- Re: [PATCH V2 12/13] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- Re: [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- Re: [PATCH V2 07/13] Add decryption support for sub-pagesized blocks
- Re: [PATCH V2 00/13] Consolidate FS read I/O callbacks code
- Re: [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- [PATCH V2 11/13] ext4: Compute logical block and the page range to be encrypted
- [PATCH V2 07/13] Add decryption support for sub-pagesized blocks
- [PATCH V2 03/13] fsverity: Add call back to decide if verity check has to be performed
- [PATCH V2 13/13] ext4: Enable encryption for subpage-sized blocks
- [PATCH V2 12/13] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- [PATCH V2 10/13] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- [PATCH V2 09/13] ext4: Decrypt the block that needs to be partially zeroed
- [PATCH V2 08/13] ext4: Decrypt all boundary blocks when doing buffered write
- [PATCH V2 06/13] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
- [PATCH V2 05/13] fs/mpage.c: Integrate read callbacks
- [PATCH V2 04/13] fsverity: Add call back to determine readpage limit
- [PATCH V2 02/13] Consolidate "read callbacks" into a new file
- [PATCH V2 01/13] ext4: Clear BH_Uptodate flag on decryption error
- [PATCH V2 00/13] Consolidate FS read I/O callbacks code
- [RFC PATCH 3/7] common/encrypt: support requiring other encryption settings
- [RFC PATCH 4/7] common/encrypt: add helper for ciphertext verification tests
- [RFC PATCH 5/7] generic: verify ciphertext of v1 encryption policies with AES-256
- [RFC PATCH 2/7] fscrypt-crypt-util: add utility for reproducing fscrypt encrypted data
- [RFC PATCH 0/7] xfstests: verify fscrypt-encrypted contents and filenames
- [RFC PATCH 6/7] generic: verify ciphertext of v1 encryption policies with AES-128
- [RFC PATCH 7/7] generic: verify ciphertext of v1 encryption policies with Adiantum
- [RFC PATCH 1/7] common/encrypt: introduce helpers for set_encpolicy and get_encpolicy
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- Re: [PATCH V1 02/14] Consolidate "post read processing" into a new file
- [PATCH V1 14/14] ext4: Enable encryption for subpage-sized blocks
- [PATCH V1 13/14] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- [PATCH V1 12/14] ext4: Compute logical block and the page range to be encrypted
- [PATCH V1 11/14] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- [PATCH V1 10/14] ext4: Decrypt the block that needs to be partially zeroed
- [PATCH V1 09/14] ext4: Decrypt all boundary blocks when doing buffered write
- [PATCH V1 08/14] Add decryption support for sub-pagesized blocks
- [PATCH V1 07/14] Remove the term "bio" from post read processing
- [PATCH V1 06/14] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
- [PATCH V1 05/14] fs/mpage.c: Integrate post read processing
- [PATCH V1 02/14] Consolidate "post read processing" into a new file
- [PATCH V1 04/14] fsverity: Add call back to determine readpage limit
- [PATCH V1 00/14] Consolidate Post read processing code
- [PATCH V1 03/14] fsverity: Add call back to decide if verity check has to be performed
- [PATCH V1 01/14] ext4: Clear BH_Uptodate flag on decryption error
- [PATCH v5 00/16] fscrypt: key management improvements
- [PATCH v5 03/16] fscrypt: use FSCRYPT_* definitions, not FS_*
- [PATCH v5 02/16] fscrypt: use FSCRYPT_ prefix for uapi constants
- [PATCH v5 04/16] fscrypt: add ->ci_inode to fscrypt_info
- [PATCH v5 05/16] fscrypt: refactor v1 policy key setup into keysetup_legacy.c
- [PATCH v5 08/16] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl
- [PATCH v5 12/16] fscrypt: require that key be added when setting a v2 encryption policy
- [PATCH v5 13/16] ext4: wire up new fscrypt ioctls
- [PATCH v5 15/16] ubifs: wire up new fscrypt ioctls
- [PATCH v5 11/16] fscrypt: allow unprivileged users to add/remove keys for v2 policies
- [PATCH v5 10/16] fscrypt: v2 encryption policy support
- [PATCH v5 07/16] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- [PATCH v5 16/16] fscrypt: document the new ioctls and policy version
- [PATCH v5 14/16] f2fs: wire up new fscrypt ioctls
- [PATCH v5 09/16] fscrypt: add an HKDF-SHA512 implementation
- [PATCH v5 06/16] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- [PATCH v5 01/16] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h>
- Re: [PATCH] ubifs: remove unnecessary #ifdef around fscrypt_ioctl_get_policy()
- Re: [PATCH] ubifs: remove unnecessary #ifdef around fscrypt_ioctl_get_policy()
- Re: [PATCH] ubifs: remove unnecessary calls to set up directory key
- Re: [PATCH v2 2/2] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link
- Re: [PATCH v2 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
- Re: [PATCH v2 4/5] fscrypt: only set dentry_operations on ciphertext dentries
- Re: [PATCH v2 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
- Re: [PATCH v2 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries
- Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- Re: [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- Re: [PATCH v2] fscrypt: use READ_ONCE() to access ->i_crypt_info
- Re: [PATCH] fscrypt: remove WARN_ON_ONCE() when decryption fails
- Re: [PATCH] fscrypt: drop inode argument from fscrypt_get_ctx()
- [RFC PATCH V2 14/14] ext4: Enable encryption for subpage-sized blocks
- [RFC PATCH V2 13/14] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- [RFC PATCH V2 12/14] ext4: Compute logical block and the page range to be encrypted
- [RFC PATCH V2 11/14] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- [RFC PATCH V2 10/14] ext4: Decrypt the block that needs to be partially zeroed
- [RFC PATCH V2 09/14] ext4: Decrypt all boundary blocks when doing buffered write
- [RFC PATCH V2 08/14] Add decryption support for sub-pagesized blocks
- [RFC PATCH V2 07/14] Remove the term "bio" from post read processing
- [RFC PATCH V2 06/14] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
- [RFC PATCH V2 05/14] fs/mpage.c: Integrate post read processing
- [RFC PATCH V2 04/14] fsverity: Add call back to determine readpage limit
- [RFC PATCH V2 03/14] fsverity: Add call back to decide if verity check has to be performed
- [RFC PATCH V2 02/14] Consolidate "post read processing" into a new file
- [RFC PATCH V2 01/14] ext4: Clear BH_Uptodate flag on decryption error
- [RFC PATCH V2 00/14] Consolidate Post read processing code
- [RFC PATCH 14/14] ext4: Enable encryption for subpage-sized blocks
- [RFC PATCH 13/14] fscrypt_zeroout_range: Encrypt all zeroed out blocks of a page
- [RFC PATCH 12/14] ext4: Compute logical block and the page range to be encrypted
- [RFC PATCH 11/14] fscrypt_encrypt_page: Loop across all blocks mapped by a page range
- [RFC PATCH 10/14] ext4: Decrypt the block that needs to be partially zeroed
- [RFC PATCH 09/14] ext4: Decrypt all boundary blocks when doing buffered write
- [RFC PATCH 08/14] Add decryption support for sub-pagesized blocks
- [RFC PATCH 07/14] Remove the term "bio" from post read processing
- [RFC PATCH 06/14] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
- [RFC PATCH 05/14] fs/mpage.c: Integrate post read processing
- [RFC PATCH 04/14] fsverity: Add call back to determine readpage limit
- [RFC PATCH 03/14] fsverity: Add call back to decide if verity check has to be performed
- [RFC PATCH 02/14] Consolidate "post read processing" into a new file
- [RFC PATCH 01/14] ext4: Clear BH_Uptodate flag on decryption error
- [RFC PATCH 00/14] Consolidate Post read processing code
- Re: [PATCH] fscrypt: add memory barrier when loading essiv_hash_tfm
- [PATCH v2] fscrypt: use READ_ONCE() to access ->i_crypt_info
- Re: [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link
- Re: [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link
- Re: [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link
- Re: [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link
- [PATCH v2 2/2] fscrypt: cache decrypted symlink target in ->i_link
- [PATCH v2 1/2] vfs: use READ_ONCE() to access ->i_link
- [PATCH v2 0/2] fscrypt: improve encrypted symlink performance
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- Re: [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- [PATCH] fscrypt: cache decrypted symlink target in ->i_link
- RE: [PATCH 0/17] Add zinc using existing algorithm implementations
- Re: [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups
- Re: [PATCH v4 07/17] fs/dcache.c: add shrink_dcache_inode()
- Re: [PATCH v4 07/17] fs/dcache.c: add shrink_dcache_inode()
- [PATCH v4 03/17] fscrypt: use FSCRYPT_* definitions, not FS_*
- [PATCH v4 06/17] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- [PATCH v4 08/17] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- [PATCH v4 10/17] fscrypt: add an HKDF-SHA512 implementation
- [PATCH v4 05/17] fscrypt: refactor v1 policy key setup into keysetup_legacy.c
- [PATCH v4 01/17] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h>
- [PATCH v4 09/17] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl
- [PATCH v4 07/17] fs/dcache.c: add shrink_dcache_inode()
- [PATCH v4 04/17] fscrypt: add ->ci_inode to fscrypt_info
- [PATCH v4 14/17] ext4: wire up new fscrypt ioctls
- [PATCH v4 17/17] fscrypt: document the new ioctls and policy version
- [PATCH v4 16/17] ubifs: wire up new fscrypt ioctls
- [PATCH v4 11/17] fscrypt: v2 encryption policy support
- [PATCH v4 12/17] fscrypt: allow unprivileged users to add/remove keys for v2 policies
- [PATCH v4 13/17] fscrypt: require that key be added when setting a v2 encryption policy
- [PATCH v4 15/17] f2fs: wire up new fscrypt ioctls
- [PATCH v4 02/17] fscrypt: use FSCRYPT_ prefix for uapi constants
- [PATCH v4 00/17] fscrypt: key management improvements
- Re: [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- [PATCH 0/2] ubifs: Get rid of some ifdefs
- [PATCH 2/2] ubifs: Remove ifdefs around CONFIG_UBIFS_ATIME_SUPPORT
- [PATCH 1/2] ubifs: Remove #ifdef around CONFIG_FS_ENCRYPTION
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- RE: [PATCH 0/17] Add zinc using existing algorithm implementations
- Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- Re: [PATCH 0/17] Add zinc using existing algorithm implementations
- [PATCH 8/17] zinc: Add generic C implementation of poly1305 and self-test
- [PATCH 12/17] zinc: BLAKE2s x86_64 implementation
- [PATCH 9/17] zinc: Add x86 accelerated poly1305
- [PATCH 15/17] zinc: import Bernstein and Schwabe's Curve25519 ARM implementation
- [PATCH 17/17] security/keys: rewrite big_key crypto to use Zinc
- [PATCH 14/17] zinc: Curve25519 x86_64 implementation
- [PATCH 7/17] crypto: poly1305 - Export core functions without crypto API
- [PATCH 5/17] zinc: Add x86 accelerated ChaCha20
- [PATCH 6/17] zinc: Add arm accelerated chacha20
- [PATCH 2/17] crypto: chacha20 - Export chacha20 functions without crypto API
- [PATCH 1/17] asm: simd context helper API
- [PATCH 3/17] zinc: introduce minimal cryptography library
- [PATCH 0/17] Add zinc using existing algorithm implementations
- [PATCH v2 1/5] fscrypt: clean up and improve dentry revalidation
- [PATCH v2 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries
- [PATCH v2 4/5] fscrypt: only set dentry_operations on ciphertext dentries
- [PATCH v2 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
- [PATCH v2 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
- [PATCH v2 0/5] fscrypt: d_revalidate fixes and cleanups
- Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- Re: [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- Re: [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- [PATCH] fscrypt: add memory barrier when loading essiv_hash_tfm
- [PATCH] fscrypt: use proper memory barriers for ->i_crypt_info
- [PATCH] fscrypt: drop inode argument from fscrypt_get_ctx()
- Re: Update fscrypt git URL for linux-next
- Re: [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- Re: Update fscrypt git URL for linux-next
- [PATCH 4/5] fscrypt: only set dentry_operations on ciphertext dentries
- [PATCH 2/5] fscrypt: fix race allowing rename() and link() of ciphertext dentries
- [PATCH 5/5] fscrypt: fix race where ->lookup() marks plaintext dentry as ciphertext
- [PATCH 1/5] fscrypt: clean up and improve dentry revalidation
- [PATCH 3/5] fs, fscrypt: clear DCACHE_ENCRYPTED_NAME when unaliasing directory
- [PATCH 0/5] fscrypt: d_revalidate fixes and cleanups
- Re: Update fscrypt git URL for linux-next
- [PATCH] fscrypt: remove WARN_ON_ONCE() when decryption fails
- Re: [PATCH] ubifs: remove unnecessary #ifdef around fscrypt_ioctl_get_policy()
- Re: [PATCH] ubifs: remove unnecessary calls to set up directory key
- [PATCH] ubifs: remove unnecessary #ifdef around fscrypt_ioctl_get_policy()
- [PATCH] ubifs: remove unnecessary calls to set up directory key
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- [PATCH] generic/398: accept EXDEV for rename or link into encrypted dir
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- Re: [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- [PATCH 4/4] ubifs: Implement new mount option, fscrypt_key_required
- [RFC] fscrypt_key_required mount option
- [PATCH 3/4] ubifs: Simplify fscrypt_get_encryption_info() error handling
- [PATCH 2/4] fscrypt: Export fscrypt_d_ops
- [PATCH 1/4] fscrypt: Implement FS_CFLG_OWN_D_OPS
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- Re: overlayfs vs. fscrypt
- overlayfs vs. fscrypt
- Update fscrypt git URL for linux-next
- Re: [GIT PULL] fscrypt updates for v5.1
- [GIT PULL] fscrypt updates for v5.1
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- Re: [RFC PATCH 08/10] fsverity: Add call back to verify file holes
- Re: [f2fs-dev] [RFC PATCH 06/10] Introduce REQ_POST_READ_PROC bio flag
- Re: [RFC PATCH 04/10] Consolidate "post read processing" into a new file
- Re: [f2fs-dev] [RFC PATCH 05/10] fsverity: Add call back to decide if verity check has to be performed
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- Re: [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- Re: [RFC PATCH v3 04/18] fs: add ->s_master_keys to struct super_block
- Re: [RFC PATCH v3 00/18] fscrypt: key management improvements
- Re: [RFC PATCH v3 00/18] fscrypt: key management improvements
- Re: [PATCH] KEYS: user: Align the payload buffer
- Re: [RFC PATCH v3 00/18] fscrypt: key management improvements
- Re: [RFC PATCH v3 00/18] fscrypt: key management improvements
- [RFC PATCH v3 04/18] fs: add ->s_master_keys to struct super_block
- [RFC PATCH v3 02/18] fscrypt: use FSCRYPT_ prefix for uapi constants
- [RFC PATCH v3 14/18] fscrypt: require that key be added when setting a v2 encryption policy
- [RFC PATCH v3 07/18] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- [RFC PATCH v3 11/18] fscrypt: add an HKDF-SHA512 implementation
- [RFC PATCH v3 13/18] fscrypt: allow unprivileged users to add/remove keys for v2 policies
- [RFC PATCH v3 15/18] ext4: wire up new fscrypt ioctls
- [RFC PATCH v3 05/18] fscrypt: add ->ci_inode to fscrypt_info
- [RFC PATCH v3 12/18] fscrypt: v2 encryption policy support
- [RFC PATCH v3 09/18] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- [RFC PATCH v3 16/18] f2fs: wire up new fscrypt ioctls
- [RFC PATCH v3 17/18] ubifs: wire up new fscrypt ioctls
- [RFC PATCH v3 18/18] fscrypt: document the new ioctls and policy version
- [RFC PATCH v3 10/18] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl
- [RFC PATCH v3 03/18] fscrypt: use FSCRYPT_* definitions, not FS_*
- [RFC PATCH v3 06/18] fscrypt: refactor v1 policy key setup into keysetup_legacy.c
- [RFC PATCH v3 08/18] fs/dcache.c: add shrink_dcache_inode()
- [RFC PATCH v3 00/18] fscrypt: key management improvements
- [RFC PATCH v3 01/18] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h>
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- Re: [RFC PATCH 08/10] fsverity: Add call back to verify file holes
- Re: [f2fs-dev] [RFC PATCH 06/10] Introduce REQ_POST_READ_PROC bio flag
- Re: [f2fs-dev] [RFC PATCH 05/10] fsverity: Add call back to decide if verity check has to be performed
- Re: [RFC PATCH 04/10] Consolidate "post read processing" into a new file
- Re: [PATCH] KEYS: user: Align the payload buffer
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- Re: [RFC PATCH 00/10] Consolidate Post read processing code
- [RFC PATCH 00/10] Consolidate Post read processing code
- [RFC PATCH 04/10] Consolidate "post read processing" into a new file
- [RFC PATCH 09/10] fs/mpage.c: Integrate post read processing
- [RFC PATCH 07/10] fsverity: Add call back to determine readpage limit
- [RFC PATCH 10/10] ext4: Wire up ext4_readpage[s] to use mpage_readpage[s]
- [RFC PATCH 08/10] fsverity: Add call back to verify file holes
- [RFC PATCH 06/10] Introduce REQ_POST_READ_PROC bio flag
- [RFC PATCH 05/10] fsverity: Add call back to decide if verity check has to be performed
- [RFC PATCH 03/10] fscrypt: remove filesystem specific build config option
- [RFC PATCH 01/10] ext4: use IS_ENCRYPTED() to check encryption status
- [RFC PATCH 02/10] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [RFC PATCH 20/27] container, keys: Add a container keyring
- Re: [f2fs-dev] Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: [RFC PATCH v2 11/20] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- Re: [RFC PATCH v2 11/20] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- Re: [RFC PATCH v2 11/20] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- [RFC PATCH v2 05/20] fscrypt: add ->ci_inode to fscrypt_info
- [RFC PATCH v2 07/20] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
- [RFC PATCH v2 12/20] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl
- [RFC PATCH v2 06/20] fscrypt: refactor v1 policy key setup into keysetup_legacy.c
- [RFC PATCH v2 10/20] fs/dcache.c: add shrink_dcache_inode()
- [RFC PATCH v2 08/20] fs/inode.c: export inode_lru_list_del()
- [RFC PATCH v2 09/20] fs/inode.c: rename and export dispose_list()
- [RFC PATCH v2 11/20] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
- [RFC PATCH v2 04/20] fs: add ->s_master_keys to struct super_block
- [RFC PATCH v2 19/20] ubifs: wire up new fscrypt ioctls
- [RFC PATCH v2 17/20] ext4: wire up new fscrypt ioctls
- [RFC PATCH v2 15/20] fscrypt: allow unprivileged users to add/remove keys for v2 policies
- [RFC PATCH v2 16/20] fscrypt: require that key be added when setting a v2 encryption policy
- [RFC PATCH v2 18/20] f2fs: wire up new fscrypt ioctls
- [RFC PATCH v2 13/20] fscrypt: add an HKDF-SHA512 implementation
- [RFC PATCH v2 20/20] fscrypt: document the new ioctls and policy version
- [RFC PATCH v2 14/20] fscrypt: v2 encryption policy support
- [RFC PATCH v2 03/20] fscrypt: use FSCRYPT_* definitions, not FS_*
- [RFC PATCH v2 01/20] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h>
- [RFC PATCH v2 02/20] fscrypt: use FSCRYPT_ prefix for uapi constants
- [RFC PATCH v2 00/20] fscrypt: key management improvements
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: Proposal: Yet another possible fs-verity interface
- Re: [PATCH] KEYS: user: Align the payload buffer
- Proposal: Yet another possible fs-verity interface
- Re: Proposal: A new fs-verity interface
- Transparent encryption mechanism
- Re: Proposal: A new fs-verity interface
- Re: Proposal: A new fs-verity interface
- Re: [PATCH] MAINTAINER: add Eric Biggers as an fscrypt maintainer
- Re: Proposal: A new fs-verity interface
- [PATCH] MAINTAINER: add Eric Biggers as an fscrypt maintainer
- Re: Proposal: A new fs-verity interface
- Re: Proposal: A new fs-verity interface
- Re: Proposal: A new fs-verity interface
- [PATCH] fscrypt: return -EXDEV for incompatible rename or link into encrypted dir
- Re: [PATCH] KEYS: user: Align the payload buffer
- [PATCH] KEYS: user: Align the payload buffer
- Re: Proposal: A new fs-verity interface
- Re: Bug report: unaligned access with ext4 encryption
- Re: Bug report: unaligned access with ext4 encryption
- Re: Bug report: unaligned access with ext4 encryption
- Re: Proposal: A new fs-verity interface
- Proposal: A new fs-verity interface
- Re: [GIT PULL] fscrypt update for 4.21
- Re: [GIT PULL] fscrypt update for 4.21
- Re: [GIT PULL] fscrypt update for 4.21
- Re: [GIT PULL] fscrypt update for 4.21
- [GIT PULL] fscrypt update for 4.21
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: Bug report: unaligned access with ext4 encryption
- Re: Bug report: unaligned access with ext4 encryption
- Re: [GIT PULL] fsverity for 4.21-rc
- [GIT PULL] fsverity for 4.21-rc
- Bug report: unaligned access with ext4 encryption
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH 5/7] generic: test corrupting verity files
- Re: [PATCH 3/7] generic: test access controls on the fs-verity ioctls
- Re: [PATCH 1/7] common/verity: add common functions for testing fs-verity
- Re: [PATCH 0/7] xfstests: add fs-verity tests
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [PATCH 0/7] xfstests: add fs-verity tests
- Re: [PATCH v2 01/12] fs-verity: add a documentation file
- Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
- Re: [PATCH 0/2] fs-verity: fix !CONFIG_FS_VERITY case
- Re: [PATCH 0/7] xfstests: add fs-verity tests
- Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
- Re: [PATCH 0/2] fs-verity: fix !CONFIG_FS_VERITY case
- Re: [PATCH] fscrypt: remove CRYPTO_CTR dependency
- Re: [PATCH 0/2] fs-verity: fix !CONFIG_FS_VERITY case
- Re: [PATCH 0/2] fs-verity: fix !CONFIG_FS_VERITY case
- [PATCH 1/2] fsverity: Move verity status check to fsverity_file_open
- [PATCH 2/2] fsverity: Move verity status check to fsverity_prepare_setattr
- [PATCH 0/2] fs-verity: fix !CONFIG_FS_VERITY case
- Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
- Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
- Re: [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
- Re: [PATCH 0/7] xfstests: add fs-verity tests
- [BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
- From: Krzysztof Kozlowski
- Re: [PATCH 0/7] xfstests: add fs-verity tests
- [PATCH 6/7] generic: test that fs-verity is using the correct measurement values
- [PATCH 7/7] generic: test using fs-verity and fscrypt simultaneously
- [PATCH 5/7] generic: test corrupting verity files
- [PATCH 4/7] generic: test fs-verity descriptor validation
- [PATCH 2/7] generic: test general behavior of verity files
- [PATCH 3/7] generic: test access controls on the fs-verity ioctls
- [PATCH 1/7] common/verity: add common functions for testing fs-verity
- [PATCH 0/7] xfstests: add fs-verity tests
- Re: [PATCH v4] fscrypt: add Adiantum support
- [PATCH -next] fsverity: fix Documentation typo
- Re: [PATCH] fscrypt: remove CRYPTO_CTR dependency
- Re: [PATCH v4 00/14] crypto: Adiantum support
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity status
- Re: [PATCH 7/7] fsverity: Remove filesystem specific build config option
- Re: [PATCH 4/7] Add S_VERITY and IS_VERITY()
- Re: [PATCH 3/7] fscrypt: Remove filesystem specific build config option
- Re: [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity status
- Re: [PATCH 7/7] fsverity: Remove filesystem specific build config option
- Re: [PATCH 6/7] f2fs: use IS_VERITY() to check inode's fsverity status
- Re: [PATCH 1/7] ext4: use IS_ENCRYPTED() to check encryption status
- Re: [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity status
- Re: [PATCH 3/7] fscrypt: Remove filesystem specific build config option
- Re: [PATCH 4/7] Add S_VERITY and IS_VERITY()
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- [PATCH v4] fscrypt: add Adiantum support
- Re: [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity status
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [PATCH v4 00/14] crypto: Adiantum support
- [v2 PATCH 3/4] zinc: Add x86 accelerated ChaCha20
- [v2 PATCH 1/4] crypto: chacha20 - Export chacha20 functions without crypto API
- [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [f2fs-dev] [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [f2fs-dev] [PATCH 6/7] f2fs: use IS_VERITY() to check inode's fsverity status
- Re: [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- Re: [RFC PATCH] zinc chacha20 generic implementation using crypto API code
- [PATCH 6/7] f2fs: use IS_VERITY() to check inode's fsverity status
- [PATCH 7/7] fsverity: Remove filesystem specific build config option
- [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity status
- [PATCH 3/7] fscrypt: Remove filesystem specific build config option
- [PATCH 4/7] Add S_VERITY and IS_VERITY()
- [PATCH 2/7] f2fs: use IS_ENCRYPTED() to check encryption status
- [PATCH 1/7] ext4: use IS_ENCRYPTED() to check encryption status
- [PATCH 0/7] Remove fs specific fscrypt and fsverity build config options
- Re: [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [PATCH v4 14/14] crypto: adiantum - add Adiantum support
- Re: [PATCH v4 13/14] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- Re: [PATCH v4 12/14] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [PATCH v4 11/14] crypto: poly1305 - add Poly1305 core API
- Re: [PATCH v4 10/14] crypto: poly1305 - use structures for key and accumulator
- [PATCH v4 02/14] crypto: chacha20-generic - don't unnecessarily use atomic walk
- [PATCH v4 01/14] crypto: chacha20-generic - add HChaCha20 library function
- [PATCH v4 06/14] crypto: arm/chacha20 - limit the preemption-disabled section
- [PATCH v4 07/14] crypto: arm/chacha20 - add XChaCha20 support
- [PATCH v4 05/14] crypto: chacha - add XChaCha12 support
- [PATCH v4 11/14] crypto: poly1305 - add Poly1305 core API
- [PATCH v4 03/14] crypto: chacha20-generic - add XChaCha20 support
- [PATCH v4 10/14] crypto: poly1305 - use structures for key and accumulator
- [PATCH v4 13/14] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- [PATCH v4 14/14] crypto: adiantum - add Adiantum support
- [PATCH v4 12/14] crypto: nhpoly1305 - add NHPoly1305 support
- [PATCH v4 09/14] crypto: arm/chacha - add XChaCha12 support
- [PATCH v4 04/14] crypto: chacha20-generic - refactor to allow varying number of rounds
- [PATCH v4 08/14] crypto: arm/chacha20 - refactor to allow varying number of rounds
- [PATCH v4 00/14] crypto: Adiantum support
- Re: [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- Re: [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- Re: [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- Re: [RFC PATCH v3 00/15] crypto: Adiantum support
- Re: [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- Re: [RFC PATCH v3 08/15] crypto: arm/chacha20 - refactor to allow varying number of rounds
- Re: [RFC PATCH v3 07/15] crypto: arm/chacha20 - add XChaCha20 support
- [RFC PATCH v2 1/2] fscrypt: remove d_lock on reading DCACHE_ENCRYPTED_WITH_KEY
- [RFC PATCH v2 2/2] fscrypt: enable RCU-walk path for .d_revalidate
- Re: [PATCH v2 10/12] ext4: add basic fs-verity support
- Re: [PATCH v2 10/12] ext4: add basic fs-verity support
- Re: [PATCH v2 10/12] ext4: add basic fs-verity support
- [RFC PATCH v3 02/15] crypto: chacha20-generic - don't unnecessarily use atomic walk
- [RFC PATCH v3 00/15] crypto: Adiantum support
- [RFC PATCH v3 01/15] crypto: chacha20-generic - add HChaCha20 library function
- [RFC PATCH v3 04/15] crypto: chacha20-generic - refactor to allow varying number of rounds
- [RFC PATCH v3 08/15] crypto: arm/chacha20 - refactor to allow varying number of rounds
- [RFC PATCH v3 07/15] crypto: arm/chacha20 - add XChaCha20 support
- [RFC PATCH v3 05/15] crypto: chacha - add XChaCha12 support
- [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
- [RFC PATCH v3 11/15] crypto: poly1305 - add Poly1305 core API
- [RFC PATCH v3 03/15] crypto: chacha20-generic - add XChaCha20 support
- [RFC PATCH v3 06/15] crypto: arm/chacha20 - limit the preemption-disabled section
- [RFC PATCH v3 13/15] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- [RFC PATCH v3 09/15] crypto: arm/chacha - add XChaCha12 support
- [RFC PATCH v3 12/15] crypto: nhpoly1305 - add NHPoly1305 support
- [RFC PATCH v3 14/15] crypto: adiantum - add Adiantum support
- [RFC PATCH v3 15/15] fscrypt: add Adiantum support
- Re: [PATCH v2 10/12] ext4: add basic fs-verity support
- Re: [PATCH v2 10/12] ext4: add basic fs-verity support
- [PATCH v2 04/12] fs-verity: add data verification hooks for ->readpages()
- [PATCH v2 00/12] fs-verity: read-only file-based authenticity protection
- [PATCH v2 01/12] fs-verity: add a documentation file
- [PATCH v2 02/12] fs-verity: add setup code, UAPI, and Kconfig
- [PATCH v2 06/12] fs-verity: implement FS_IOC_MEASURE_VERITY ioctl
- [PATCH v2 08/12] fs-verity: add CRC-32C support
- [PATCH v2 07/12] fs-verity: add SHA-512 support
- [PATCH v2 09/12] fs-verity: support builtin file signatures
- [PATCH v2 10/12] ext4: add basic fs-verity support
- [PATCH v2 11/12] ext4: add fs-verity read support
- [PATCH v2 12/12] f2fs: fs-verity support
- [PATCH v2 05/12] fs-verity: implement FS_IOC_ENABLE_VERITY ioctl
- [PATCH v2 03/12] fs-verity: add MAINTAINERS file entry
- Re: [RFC PATCH 1/2] fscrypt: Remove filesystem specific build config option
- Re: [RFC PATCH 1/2] fscrypt: Remove filesystem specific build config option
- [RFC PATCH 2/2] fsverity: Remove filesystem specific build config option
- [RFC PATCH 1/2] fscrypt: Remove filesystem specific build config option
- Re: [RFC PATCH v2 11/12] crypto: adiantum - add Adiantum support
- Re: [RFC PATCH v2 11/12] crypto: adiantum - add Adiantum support
- Re: [RFC PATCH v2 11/12] crypto: adiantum - add Adiantum support
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 10/12] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 11/12] crypto: adiantum - add Adiantum support
- Re: [RFC PATCH v2 10/12] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 06/12] crypto: arm/chacha20 - refactor to allow varying number of rounds
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 11/12] crypto: adiantum - add Adiantum support
- Re: [RFC PATCH v2 10/12] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- Re: [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- Re: [RFC PATCH v2 08/12] crypto: poly1305 - add Poly1305 core API
- Re: [RFC PATCH v2 07/12] crypto: arm/chacha - add XChaCha12 support
- Re: [RFC PATCH v2 06/12] crypto: arm/chacha20 - refactor to allow varying number of rounds
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 05/12] crypto: arm/chacha20 - add XChaCha20 support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 04/12] crypto: chacha - add XChaCha12 support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH v2 04/12] crypto: chacha - add XChaCha12 support
- Re: [RFC PATCH v2 03/12] crypto: chacha20-generic - refactor to allow varying number of rounds
- Re: [RFC PATCH v2 02/12] crypto: chacha20-generic - add XChaCha20 support
- Re: [RFC PATCH v2 01/12] crypto: chacha20-generic - add HChaCha20 library function
- [RFC PATCH v2 02/12] crypto: chacha20-generic - add XChaCha20 support
- [RFC PATCH v2 03/12] crypto: chacha20-generic - refactor to allow varying number of rounds
- [RFC PATCH v2 01/12] crypto: chacha20-generic - add HChaCha20 library function
- [RFC PATCH v2 04/12] crypto: chacha - add XChaCha12 support
- [RFC PATCH v2 06/12] crypto: arm/chacha20 - refactor to allow varying number of rounds
- [RFC PATCH v2 07/12] crypto: arm/chacha - add XChaCha12 support
- [RFC PATCH v2 05/12] crypto: arm/chacha20 - add XChaCha20 support
- [RFC PATCH v2 08/12] crypto: poly1305 - add Poly1305 core API
- [RFC PATCH v2 12/12] fscrypt: add Adiantum support
- [RFC PATCH v2 10/12] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
- [RFC PATCH v2 09/12] crypto: nhpoly1305 - add NHPoly1305 support
- [RFC PATCH v2 11/12] crypto: adiantum - add Adiantum support
- [RFC PATCH v2 00/12] crypto: Adiantum support
- Re: [RFC PATCH 01/10] fs-verity: add setup code, UAPI, and Kconfig
- Re: [RFC PATCH 01/10] fs-verity: add setup code, UAPI, and Kconfig
- Re: [RFC PATCH 01/10] fs-verity: add setup code, UAPI, and Kconfig
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[Linux Kernel]
[Fedora Users]
[Yosemite Campsites]