Filesystem Crypto
[Prev Page][Next Page]
- Re: [GIT PULL] fscrypt update for 6.10
- [GIT PULL] fscrypt update for 6.10
- Re: [PATCH v2] fscrypt: try to avoid refing parent dentry in fscrypt_file_open
- [PATCH v2] fscrypt: try to avoid refing parent dentry in fscrypt_file_open
- Re: [PATCH] fscrypto: try to avoid refing parent dentry in fscrypt_file_open
- [PATCH] fscrypto: try to avoid refing parent dentry in fscrypt_file_open
- [linux-next:master] BUILD REGRESSION d04466706db5e241ee026f17b5f920e50dee26b5
- Re: [PATCH 3/6] memory-failure: Remove calls to page_mapping()
- Re: [PATCH 6/6] mm: Remove page_mapping()
- Re: [PATCH 6/6] mm: Remove page_mapping()
- Re: [PATCH 6/6] mm: Remove page_mapping()
- Re: [PATCH 5/6] userfault; Expand folio use in mfill_atomic_install_pte()
- Re: [PATCH 4/6] migrate: Expand the use of folio in __migrate_device_pages()
- Re: [PATCH 3/6] memory-failure: Remove calls to page_mapping()
- Re: [PATCH 2/6] f2fs: Convert f2fs_clear_page_cache_dirty_tag to use a folio
- Re: [PATCH 1/6] fscrypt: Convert bh_get_inode_and_lblk_num to use a folio
- Re: [PATCH 3/6] memory-failure: Remove calls to page_mapping()
- Re: [PATCH 1/6] fscrypt: Convert bh_get_inode_and_lblk_num to use a folio
- [PATCH 5/6] userfault; Expand folio use in mfill_atomic_install_pte()
- From: Matthew Wilcox (Oracle)
- [PATCH 0/6] Remove page_mapping()
- From: Matthew Wilcox (Oracle)
- [PATCH 6/6] mm: Remove page_mapping()
- From: Matthew Wilcox (Oracle)
- [PATCH 1/6] fscrypt: Convert bh_get_inode_and_lblk_num to use a folio
- From: Matthew Wilcox (Oracle)
- [PATCH 2/6] f2fs: Convert f2fs_clear_page_cache_dirty_tag to use a folio
- From: Matthew Wilcox (Oracle)
- [PATCH 4/6] migrate: Expand the use of folio in __migrate_device_pages()
- From: Matthew Wilcox (Oracle)
- [PATCH 3/6] memory-failure: Remove calls to page_mapping()
- From: Matthew Wilcox (Oracle)
- Re: [PATCH v4 00/46] btrfs: add fscrypt support
- Re: [PATCH v4 00/46] btrfs: add fscrypt support
- Re: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc
- Bug#1066832: Info received (Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc)
- From: Debian Bug Tracking System
- Re: Debian #1066832: [fsverity-utils] hard Build-Depends on unportable package pandoc
- Re: [GIT PULL] fscrypt updates for 6.9
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- [GIT PULL] fscrypt updates for 6.9
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v14 05/19] initramfs|security: Add a security hook to do_populate_rootfs()
- Re: [RFC PATCH v14 01/19] security: add ipe lsm
- Re: [RFC PATCH v14 05/19] initramfs|security: Add a security hook to do_populate_rootfs()
- Re: [RFC PATCH v14 01/19] security: add ipe lsm
- Re: [RFC PATCH v14 00/19] Integrity Policy Enforcement LSM (IPE)
- Re: [RFC PATCH v14 17/19] scripts: add boot policy generation program
- Re: [RFC PATCH v14 16/19] ipe: enable support for fs-verity as a trust provider
- Re: [RFC PATCH v14 14/19] ipe: add support for dm-verity as a trust provider
- [RFC PATCH v14 19/19] documentation: add ipe documentation
- [RFC PATCH v14 17/19] scripts: add boot policy generation program
- [RFC PATCH v14 08/19] ipe: add userspace interface
- [RFC PATCH v14 16/19] ipe: enable support for fs-verity as a trust provider
- [RFC PATCH v14 11/19] block|security: add LSM blob to block_device
- [RFC PATCH v14 14/19] ipe: add support for dm-verity as a trust provider
- [RFC PATCH v14 18/19] ipe: kunit test for parser
- [RFC PATCH v14 15/19] fsverity: consume builtin signature via LSM hook
- [RFC PATCH v14 13/19] dm verity: consume root hash digest and signature data via LSM hook
- [RFC PATCH v14 09/19] uapi|audit|ipe: add ipe auditing support
- [RFC PATCH v14 12/19] dm: add finalize hook to target_type
- [RFC PATCH v14 06/19] ipe: introduce 'boot_verified' as a trust provider
- [RFC PATCH v14 10/19] ipe: add permissive toggle
- [RFC PATCH v14 07/19] security: add new securityfs delete function
- [RFC PATCH v14 05/19] initramfs|security: Add a security hook to do_populate_rootfs()
- [RFC PATCH v14 02/19] ipe: add policy parser
- [RFC PATCH v14 03/19] ipe: add evaluation loop
- [RFC PATCH v14 00/19] Integrity Policy Enforcement LSM (IPE)
- [RFC PATCH v14 04/19] ipe: add LSM hooks on execution and kernel read
- [RFC PATCH v14 01/19] security: add ipe lsm
- [PATCH] ceph: return -ENODATA when xattr doesn't exist for removexattr
- [syzbot] [fscrypt?] possible deadlock in fscrypt_setup_encryption_info
- Re: [RFC PATCH v13 14/20] dm verity: consume root hash digest and signature data via LSM hook
- Re: [RFC PATCH v13 14/20] dm verity: consume root hash digest and signature data via LSM hook
- Re: [RFC PATCH v13 13/20] dm: add finalize hook to target_type
- Re: [RFC PATCH v13 12/20] dm verity: set DM_TARGET_SINGLETON feature flag
- Re: [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider
- Re: [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider
- Re: [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider
- Re: [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider
- Re: [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider
- [RFC PATCH v13 20/20] documentation: add ipe documentation
- [RFC PATCH v13 17/20] ipe: enable support for fs-verity as a trust provider
- [RFC PATCH v13 09/20] uapi|audit|ipe: add ipe auditing support
- [RFC PATCH v13 19/20] ipe: kunit test for parser
- [RFC PATCH v13 15/20] ipe: add support for dm-verity as a trust provider
- [RFC PATCH v13 18/20] scripts: add boot policy generation program
- [RFC PATCH v13 11/20] block|security: add LSM blob to block_device
- [RFC PATCH v13 08/20] ipe: add userspace interface
- [RFC PATCH v13 16/20] fsverity: consume builtin signature via LSM hook
- [RFC PATCH v13 12/20] dm verity: set DM_TARGET_SINGLETON feature flag
- [RFC PATCH v13 14/20] dm verity: consume root hash digest and signature data via LSM hook
- [RFC PATCH v13 13/20] dm: add finalize hook to target_type
- [RFC PATCH v13 10/20] ipe: add permissive toggle
- [RFC PATCH v13 07/20] security: add new securityfs delete function
- [RFC PATCH v13 06/20] ipe: introduce 'boot_verified' as a trust provider
- [RFC PATCH v13 05/20] initramfs|security: Add a security hook to do_populate_rootfs()
- [RFC PATCH v13 01/20] security: add ipe lsm
- [RFC PATCH v13 00/20] Integrity Policy Enforcement LSM (IPE)
- [RFC PATCH v13 04/20] ipe: add LSM hooks on execution and kernel read
- [RFC PATCH v13 02/20] ipe: add policy parser
- [RFC PATCH v13 03/20] ipe: add evaluation loop
- [PATCH] fscrypt: shrink the size of struct fscrypt_inode_info slightly
- [PATCH] fscrypt: write CBC-CTS instead of CTS-CBC
- Re: [PATCH] fscrypt: clear keyring before calling key_put()
- Re: [PATCH] fscrypt: clear keyring before calling key_put()
- Re: [PATCH RFC v12 15/20] ipe: add support for dm-verity as a trust provider
- [PATCH] fscrypt: clear keyring before calling key_put()
- Re: [PATCH RFC v12 8/20] ipe: add userspace interface
- Re: [PATCH RFC v12 15/20] ipe: add support for dm-verity as a trust provider
- Re: [PATCH RFC v12 8/20] ipe: add userspace interface
- Re: [PATCH RFC v12 8/20] ipe: add userspace interface
- Re: [PATCH RFC v12 6/20] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v12 5/20] initramfs|security: Add security hook to initramfs unpack
- Re: [PATCH RFC v12 17/20] ipe: enable support for fs-verity as a trust provider
- Re: [PATCH RFC v12 15/20] ipe: add support for dm-verity as a trust provider
- Re: [PATCH RFC v12 9/20] uapi|audit|ipe: add ipe auditing support
- Re: [PATCH RFC v12 10/20] ipe: add permissive toggle
- Re: [PATCH RFC v12 8/20] ipe: add userspace interface
- Re: [PATCH RFC v12 6/20] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v12 5/20] initramfs|security: Add security hook to initramfs unpack
- Re: [RFC PATCH v12 12/20] dm verity: set DM_TARGET_SINGLETON feature flag
- Re: [RFC PATCH v12 12/20] dm verity: set DM_TARGET_SINGLETON feature flag
- Re: [PATCH v2] fscrypt: to make sure the inode->i_blkbits is correctly set
- Re: [PATCH v2] fscrypt: to make sure the inode->i_blkbits is correctly set
- [PATCH v2] fscrypt: to make sure the inode->i_blkbits is correctly set
- Re: [PATCH] fscrypt: to make sure the inode->i_blkbits is correctly set
- [RFC PATCH v12 20/20] documentation: add ipe documentation
- [RFC PATCH v12 19/20] ipe: kunit test for parser
- [RFC PATCH v12 17/20] ipe: enable support for fs-verity as a trust provider
- [RFC PATCH v12 15/20] ipe: add support for dm-verity as a trust provider
- [RFC PATCH v12 08/20] ipe: add userspace interface
- [RFC PATCH v12 18/20] scripts: add boot policy generation program
- [RFC PATCH v12 11/20] block|security: add LSM blob to block_device
- [RFC PATCH v12 16/20] fsverity: consume builtin signature via LSM hook
- [RFC PATCH v12 14/20] dm verity: consume root hash digest and signature data via LSM hook
- [RFC PATCH v12 12/20] dm verity: set DM_TARGET_SINGLETON feature flag
- [RFC PATCH v12 09/20] uapi|audit|ipe: add ipe auditing support
- [RFC PATCH v12 10/20] ipe: add permissive toggle
- [RFC PATCH v12 13/20] dm: add finalize hook to target_type
- [RFC PATCH v12 07/20] security: add new securityfs delete function
- [RFC PATCH v12 06/20] ipe: introduce 'boot_verified' as a trust provider
- [RFC PATCH v12 05/20] initramfs|security: Add security hook to initramfs unpack
- [RFC PATCH v12 04/20] ipe: add LSM hooks on execution and kernel read
- [RFC PATCH v12 03/20] ipe: add evaluation loop
- [RFC PATCH v12 02/20] ipe: add policy parser
- [RFC PATCH v12 00/20] Integrity Policy Enforcement LSM (IPE)
- [RFC PATCH v12 01/20] security: add ipe lsm
- Re: [PATCH] fscrypt: to make sure the inode->i_blkbits is correctly set
- [PATCH] fscrypt: to make sure the inode->i_blkbits is correctly set
- Re: [PATCH v3 04/10] fscrypt: Drop d_revalidate once the key is added
- From: Gabriel Krisman Bertazi
- Re: [PATCH v3 04/10] fscrypt: Drop d_revalidate once the key is added
- Re: [syzbot] [f2fs?] KASAN: slab-use-after-free Read in kill_f2fs_super
- Re: [GIT PULL] fscrypt fix for 6.8-rc1
- Re: [f2fs-dev] [PATCH v2 0/2] Move fscrypt keyring destruction to after ->put_super
- RE: [PATCH v6 RESEND 5/5] crypto: LEA block cipher x86_64 optimization
- Re: [PATCH v2 4/4] generic: add test for custom crypto data unit size
- [GIT PULL] fscrypt fix for 6.8-rc1
- Re: [syzbot] [f2fs?] KASAN: slab-use-after-free Read in kill_f2fs_super
- Re: [PATCH] f2fs: fix double free of f2fs_sb_info
- Re: [PATCH] f2fs: fix double free of f2fs_sb_info
- Re: [PATCH] f2fs: fix double free of f2fs_sb_info
- Re: [f2fs-dev] [PATCH] f2fs: fix double free of f2fs_sb_info
- Re: [PATCH] f2fs: fix double free of f2fs_sb_info
- [PATCH] f2fs: fix double free of f2fs_sb_info
- Re: [PATCH v2 0/4] xfstests: test custom crypto data unit size
- RE: [PATCH v6 RESEND 5/5] crypto: LEA block cipher x86_64 optimization
- [PATCH v6 RESEND 5/5] crypto: LEA block cipher x86_64 optimization
- [PATCH v6 RESEND 4/5] fscrypt: Add LEA-256-XTS, LEA-256-CTS support
- [PATCH v6 RESEND 3/5] blk-crypto: Add LEA-256-XTS blk-crypto support
- [PATCH v6 RESEND 2/5] crypto: add LEA testmgr tests
- [PATCH v6 RESEND 1/5] crypto: LEA block cipher implementation
- [PATCH v6 RESEND 0/5] crypto: LEA block cipher implementation
- Re: [PATCH v2 0/4] xfstests: test custom crypto data unit size
- Re: [GIT PULL] fscrypt updates for 6.8
- [GIT PULL] fscrypt updates for 6.8
- [PATCH v3 1/2] ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed
- [PATCH v3 0/2] ubifs: Fix two kmemleaks in error path
- [PATCH v3 2/2] ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
- Re: [PATCH v2 1/2] ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed
- Re: [f2fs-dev] [PATCH v2 1/2] f2fs: move release of block devices to after kill_block_super()
- [PATCH v2 1/2] f2fs: move release of block devices to after kill_block_super()
- [PATCH v2 2/2] fs: move fscrypt keyring destruction to after ->put_super
- [PATCH v2 0/2] Move fscrypt keyring destruction to after ->put_super
- Re: [f2fs-dev] [PATCH 2/3] f2fs: move release of block devices to after kill_block_super()
- [PATCH] fscrypt: document that CephFS supports fscrypt now
- Re: [PATCH 2/3] f2fs: move release of block devices to after kill_block_super()
- Re: [PATCH v2 2/2] ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
- [PATCH v2 0/2] ubifs: Fix two kmemleaks in error path
- [PATCH v2 2/2] ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
- [PATCH v2 1/2] ubifs: dbg_check_idx_size: Fix kmemleak if loading znode failed
- Re: Performance drop due to alloc_workqueue() misuse and recent change
- Question about CNC
- RE: [PATCH v6 0/5] crypto: LEA block cipher implementation
- Re: [f2fs-dev] [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb
- Re: [f2fs-dev] [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb
- Re: [f2fs-dev] [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb
- Re: [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb
- Re: [PATCH 3/3] fs: move fscrypt keyring destruction to after ->put_super
- Re: [PATCH 3/3] fs: move fscrypt keyring destruction to after ->put_super
- Re: [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb
- Re: [PATCH v3 07/12] qcom_scm: scm call for create, prepare and import keys
- [PATCH 3/3] fs: move fscrypt keyring destruction to after ->put_super
- [PATCH 1/3] btrfs: call btrfs_close_devices from ->kill_sb
- [PATCH 2/3] f2fs: move release of block devices to after kill_block_super()
- [PATCH 0/3] Move fscrypt keyring destruction to after ->put_super
- RE: [PATCH v3 02/12] qcom_scm: scm call for deriving a software secret
- RE: [PATCH v3 04/12] soc: qcom: ice: support for hardware wrapped keys
- RE: [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- RE: [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- Re: [PATCH v3 11/12] arm64: dts: qcom: sm8650: add hwkm support to ufs ice
- Re: [PATCH v3 11/12] arm64: dts: qcom: sm8650: add hwkm support to ufs ice
- Re: [PATCH v3 09/12] soc: qcom: support for generate, import and prepare key
- Re: [PATCH v3 10/12] ufs: host: support for generate, import and prepare key
- Re: [PATCH v3 08/12] ufs: core: add support for generate, import and prepare keys
- Re: [PATCH v3 06/12] ufs: host: wrapped keys support in ufs qcom
- Re: [PATCH v3 04/12] soc: qcom: ice: support for hardware wrapped keys
- Re: [PATCH v3 02/12] qcom_scm: scm call for deriving a software secret
- Re: [PATCH v3 01/12] ice, ufs, mmc: use blk_crypto_key for program_key
- Re: [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- Re: [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- Re: [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- Re: [PATCH v3 12/12] dt-bindings: crypto: ice: document the hwkm property
- Re: [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- Re: [PATCH v3 11/12] arm64: dts: qcom: sm8650: add hwkm support to ufs ice
- Re: [PATCH v3 08/12] ufs: core: add support for generate, import and prepare keys
- Re: [PATCH v3 05/12] ufs: core: support wrapped keys in ufs core
- Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- [PATCH] fscrypt: update comment for do_remove_key()
- Re: [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- [PATCH] fscrypt.rst: update definition of struct fscrypt_context_v2
- [PATCH] fscrypt: move the call to fscrypt_destroy_keyring() into ->put_super()
- Re: [PATCH v3 00/12] Hardware wrapped key support for qcom ice and ufs
- [PATCH v6 0/5] crypto: LEA block cipher implementation
- [PATCH v6 3/5] blk-crypto: Add LEA-256-XTS blk-crypto support
- [PATCH v6 5/5] crypto: LEA block cipher x86_64 optimization
- [PATCH v6 2/5] crypto: add LEA testmgr tests
- [PATCH v6 1/5] crypto: LEA block cipher implementation
- [PATCH v6 4/5] fscrypt: Add LEA-256-XTS, LEA-256-CTS support
- Re: Performance drop due to alloc_workqueue() misuse and recent change
- Performance drop due to alloc_workqueue() misuse and recent change
- Re: [PATCH v4 00/46] btrfs: add fscrypt support
- Re: [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size
- Re: [syzbot] [fscrypt?] possible deadlock in find_and_lock_process_key
- Re: [syzbot] [fscrypt?] possible deadlock in fscrypt_initialize (2)
- Re: [PATCH 07/12] btrfs: test snapshotting encrypted subvol
- Re: [PATCH 07/12] btrfs: test snapshotting encrypted subvol
- [syzbot] [fscrypt?] possible deadlock in find_and_lock_process_key
- Re: [PATCH] ceph: select FS_ENCRYPTION_ALGS if FS_ENCRYPTION
- Re: [PATCH] ceph: select FS_ENCRYPTION_ALGS if FS_ENCRYPTION
- [PATCH] ceph: select FS_ENCRYPTION_ALGS if FS_ENCRYPTION
- Re: [PATCH v3 02/12] qcom_scm: scm call for deriving a software secret
- Re: [PATCH 09/12] fstests: split generic/580 into two tests
- Re: [PATCH v2 00/36] btrfs: add fscrypt support
- Re: [PATCH v3 00/12] Hardware wrapped key support for qcom ice and ufs
- From: Krzysztof Kozlowski
- Re: [PATCH v3 12/12] dt-bindings: crypto: ice: document the hwkm property
- From: Krzysztof Kozlowski
- [PATCH v3 07/12] qcom_scm: scm call for create, prepare and import keys
- [PATCH v3 12/12] dt-bindings: crypto: ice: document the hwkm property
- [PATCH v3 05/12] ufs: core: support wrapped keys in ufs core
- [PATCH v3 08/12] ufs: core: add support for generate, import and prepare keys
- [PATCH v3 09/12] soc: qcom: support for generate, import and prepare key
- [PATCH v3 11/12] arm64: dts: qcom: sm8650: add hwkm support to ufs ice
- [PATCH v3 06/12] ufs: host: wrapped keys support in ufs qcom
- [PATCH v3 04/12] soc: qcom: ice: support for hardware wrapped keys
- [PATCH v3 10/12] ufs: host: support for generate, import and prepare key
- [PATCH v3 03/12] soc: qcom: ice: add hwkm support in ice
- [PATCH v3 00/12] Hardware wrapped key support for qcom ice and ufs
- [PATCH v3 02/12] qcom_scm: scm call for deriving a software secret
- [PATCH v3 01/12] ice, ufs, mmc: use blk_crypto_key for program_key
- Re: [PATCH v2 00/36] btrfs: add fscrypt support
- [PATCH 02/14] tools headers UAPI: Update tools's copy of fscrypt.h header
- [PATCH v2 4/4] generic: add test for custom crypto data unit size
- [PATCH v2 3/4] common/encrypt: support custom data unit size
- [PATCH v2 0/4] xfstests: test custom crypto data unit size
- [PATCH v2 2/4] common/rc: fix _require_xfs_io_command with digits in argument
- [PATCH v2 1/4] fscrypt-crypt-util: rename block to data unit
- Re: [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size
- Re: [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size
- Re: [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size
- Re: PSA: This list is being migrated (no action required)
- From: Konstantin Ryabitsev
- PSA: This list is being migrated (no action required)
- From: Konstantin Ryabitsev
- Re: [PATCH 09/12] fstests: split generic/580 into two tests
- Re: [PATCH 12/12] fstest: add a fsstress+fscrypt test
- PSA: migrating linux-fscrypt to new vger infrastructure
- From: Konstantin Ryabitsev
- [RFC PATCH v8 4/4] fscrypt: add support for hardware-wrapped keys
- [RFC PATCH v8 1/4] blk-crypto: add basic hardware-wrapped key support
- [RFC PATCH v8 3/4] blk-crypto: add ioctls to create and prepare hardware-wrapped keys
- [RFC PATCH v8 2/4] blk-crypto: show supported key types in sysfs
- [RFC PATCH v8 0/4] Support for hardware-wrapped inline encryption keys
- Re: [PATCH RFC v11 5/19] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v11 5/19] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v11 18/19] ipe: kunit test for parser
- Re: [PATCH RFC v11 17/19] scripts: add boot policy generation program
- Re: [PATCH RFC v11 9/19] ipe: add permissive toggle
- Re: [PATCH RFC v11 8/19] uapi|audit|ipe: add ipe auditing support
- Re: [PATCH RFC v11 5/19] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v11 14/19] ipe: add support for dm-verity as a trust provider
- Re: [PATCH RFC v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: [PATCH RFC v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: [PATCH 09/12] fstests: split generic/580 into two tests
- Re: [PATCH RFC v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: [PATCH RFC v11 13/19] dm verity: consume root hash digest and signature data via LSM hook
- Re: [PATCH RFC v11 12/19] dm: add finalize hook to target_type
- Re: [PATCH RFC v11 11/19] dm verity: set DM_TARGET_SINGLETON feature flag
- Re: [PATCH RFC v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: [PATCH 08/12] fstests: properly test for v1 encryption policies in encrypt tests
- Re: [PATCH 07/12] btrfs: test snapshotting encrypted subvol
- Re: [PATCH 07/12] btrfs: test snapshotting encrypted subvol
- Re: [PATCH 05/12] common/verity: explicitly don't allow btrfs encryption
- Re: [PATCH 04/12] common/encrypt: enable making a encrypted btrfs filesystem
- Re: [PATCH 03/12] common/encrypt: add btrfs to get_ciphertext_filename
- Re: [PATCH 02/12] common/encrypt: add btrfs to get_encryption_*nonce
- Re: [PATCH 01/12] common/encrypt: separate data and inode nonces
- Re: [PATCH 06/12] btrfs: add simple test of reflink of encrypted data
- Re: [GIT PULL] fscrypt updates for 6.7
- [GIT PULL] fscrypt updates for 6.7
- Re: [PATCH RFC v11 5/19] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v11 2/19] ipe: add policy parser
- Re: [PATCH RFC v11 5/19] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v11 3/19] ipe: add evaluation loop
- Re: [PATCH RFC v11 2/19] ipe: add policy parser
- Re: [PATCH RFC v11 18/19] ipe: kunit test for parser
- Re: [PATCH RFC v11 17/19] scripts: add boot policy generation program
- Re: [PATCH RFC v11 14/19] ipe: add support for dm-verity as a trust provider
- Re: [PATCH RFC v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: [PATCH RFC v11 5/19] ipe: introduce 'boot_verified' as a trust provider
- Re: [PATCH RFC v11 16/19] ipe: enable support for fs-verity as a trust provider
- Re: [PATCH RFC v11 12/19] dm: add finalize hook to target_type
- Re: [PATCH RFC v11 9/19] ipe: add permissive toggle
- Re: [PATCH RFC v11 11/19] dm verity: set DM_TARGET_SINGLETON feature flag
- Re: [PATCH RFC v11 13/19] dm verity: consume root hash digest and signature data via LSM hook
- Re: [PATCH RFC v11 8/19] uapi|audit|ipe: add ipe auditing support
- Re: [PATCH RFC v11 4/19] ipe: add LSM hooks on execution and kernel read
- Re: [PATCH RFC v11 3/19] ipe: add evaluation loop
- Re: [PATCH RFC v11 2/19] ipe: add policy parser
- Re: [PATCH 08/12] fstests: properly test for v1 encryption policies in encrypt tests
- Re: [PATCH 12/12] fstest: add a fsstress+fscrypt test
- Re: [PATCH 01/12] common/encrypt: separate data and inode nonces
- Re: [PATCH] fscrypt: track master key presence separately from secret
- Re: [PATCH] fscrypt: track master key presence separately from secret
- Re: [PATCH] fscrypt: track master key presence separately from secret
- Re: [PATCH v2 03/36] fscrypt: add per-extent encryption support
- Re: [PATCH v2 05/36] blk-crypto: add a process bio callback
- Re: [PATCH v2 04/36] fscrypt: disable all but standard v2 policies for extent encryption
- Re: [PATCH v2 02/36] fscrypt: don't wipe mk secret until the last active user is gone
- Re: [PATCH v2 01/36] fscrypt: use a flag to indicate that the master key is being evicted
- [PATCH] fscrypt: track master key presence separately from secret
- [xfsprogs PATCH] xfs_io/encrypt: support specifying crypto data unit size
- [PATCH 3/4] common/encrypt: support custom data unit size
- [PATCH 2/4] common/rc: fix _require_xfs_io_command with digits in argument
- [PATCH 4/4] generic: add test for custom crypto data unit size
- [PATCH 1/4] fscrypt-crypt-util: rename block to data unit
- [PATCH 0/4] xfstests: test custom crypto data unit size
- [PATCH v2 35/36] btrfs: add orig_logical to btrfs_bio
- [PATCH v2 30/36] btrfs: implement the fscrypt extent encryption hooks
- [PATCH v2 32/36] btrfs: populate ordered_extent with the orig offset
- [PATCH v2 31/36] btrfs: setup fscrypt_extent_info for new extents
- [PATCH v2 36/36] btrfs: implement process_bio cb for fscrypt
- [PATCH v2 29/36] btrfs: pass the fscrypt_info through the replace extent infrastructure
- [PATCH v2 34/36] btrfs: add a bio argument to btrfs_csum_one_bio
- [PATCH v2 33/36] btrfs: set the bio fscrypt context when applicable
- [PATCH v2 24/36] btrfs: populate the ordered_extent with the fscrypt context
- [PATCH v2 26/36] btrfs: add an optional encryption context to the end of file extents
- [PATCH v2 27/36] btrfs: explicitly track file extent length for replace and drop
- [PATCH v2 25/36] btrfs: keep track of fscrypt info and orig_start for dio reads
- [PATCH v2 28/36] btrfs: pass through fscrypt_extent_info to the file extent helpers
- [PATCH v2 23/36] btrfs: plumb through setting the fscrypt_info for ordered extents
- [PATCH v2 22/36] btrfs: add fscrypt_info and encryption_type to ordered_extent
- [PATCH v2 21/36] btrfs: add fscrypt_info and encryption_type to extent_map
- [PATCH v2 14/36] btrfs: adapt readdir for encrypted and nokey names
- [PATCH v2 20/36] btrfs: set file extent encryption excplicitly
- [PATCH v2 19/36] btrfs: turn on inlinecrypt mount option for encrypt
- [PATCH v2 18/36] btrfs: add get_devices hook for fscrypt
- [PATCH v2 17/36] btrfs: add encryption to CONFIG_BTRFS_DEBUG
- [PATCH v2 16/36] btrfs: implement fscrypt ioctls
- [PATCH v2 15/36] btrfs: handle nokey names.
- [PATCH v2 12/36] btrfs: add inode encryption contexts
- [PATCH v2 13/36] btrfs: add new FEATURE_INCOMPAT_ENCRYPT flag
- [PATCH v2 11/36] btrfs: start using fscrypt hooks
- [PATCH v2 10/36] btrfs: disable verity on encrypted inodes
- [PATCH v2 09/36] btrfs: disable various operations on encrypted inodes
- [PATCH v2 07/36] fscrypt: add documentation about extent encryption
- [PATCH v2 08/36] btrfs: add infrastructure for safe em freeing
- [PATCH v2 06/36] fscrypt: expose fscrypt_nokey_name
- [PATCH v2 05/36] blk-crypto: add a process bio callback
- [PATCH v2 03/36] fscrypt: add per-extent encryption support
- [PATCH v2 04/36] fscrypt: disable all but standard v2 policies for extent encryption
- [PATCH v2 02/36] fscrypt: don't wipe mk secret until the last active user is gone
- [PATCH v2 01/36] fscrypt: use a flag to indicate that the master key is being evicted
- [PATCH v2 00/36] btrfs: add fscrypt support
- [PATCH 03/12] common/encrypt: add btrfs to get_ciphertext_filename
- [PATCH 05/12] common/verity: explicitly don't allow btrfs encryption
- [PATCH 11/12] fstests: split generic/613 into two tests
- [PATCH 02/12] common/encrypt: add btrfs to get_encryption_*nonce
- [PATCH 08/12] fstests: properly test for v1 encryption policies in encrypt tests
- [PATCH 06/12] btrfs: add simple test of reflink of encrypted data
- [PATCH 09/12] fstests: split generic/580 into two tests
- [PATCH 12/12] fstest: add a fsstress+fscrypt test
- [PATCH 04/12] common/encrypt: enable making a encrypted btrfs filesystem
- [PATCH 10/12] fstests: split generic/581 into two tests
- [PATCH 07/12] btrfs: test snapshotting encrypted subvol
- [PATCH 00/12] fstests: fscrypt test updates
- [PATCH 01/12] common/encrypt: separate data and inode nonces
- Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info
- Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info
- Re: [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info
- Re: [PATCH 13/35] btrfs: adapt readdir for encrypted and nokey names
- Re: [RFC PATCH v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: Master key removal semantics
- [PATCH] fscrypt: rename fscrypt_info => fscrypt_inode_info
- Re: [RFC PATCH v11 16/19] ipe: enable support for fs-verity as a trust provider
- Re: [RFC PATCH v11 15/19] fsverity: consume builtin signature via LSM hook
- Re: [RFC PATCH v11 16/19] ipe: enable support for fs-verity as a trust provider
- [RFC PATCH v11 02/19] ipe: add policy parser
- [RFC PATCH v11 10/19] block|security: add LSM blob to block_device
- [RFC PATCH v11 19/19] documentation: add ipe documentation
- [RFC PATCH v11 11/19] dm verity: set DM_TARGET_SINGLETON feature flag
- [RFC PATCH v11 05/19] ipe: introduce 'boot_verified' as a trust provider
- [RFC PATCH v11 17/19] scripts: add boot policy generation program
- [RFC PATCH v11 04/19] ipe: add LSM hooks on execution and kernel read
- [RFC PATCH v11 12/19] dm: add finalize hook to target_type
- [RFC PATCH v11 00/19] Integrity Policy Enforcement LSM (IPE)
- [RFC PATCH v11 06/19] security: add new securityfs delete function
- [RFC PATCH v11 01/19] security: add ipe lsm
- [RFC PATCH v11 13/19] dm verity: consume root hash digest and signature data via LSM hook
- [RFC PATCH v11 18/19] ipe: kunit test for parser
- [RFC PATCH v11 07/19] ipe: add userspace interface
- [RFC PATCH v11 15/19] fsverity: consume builtin signature via LSM hook
- [RFC PATCH v11 14/19] ipe: add support for dm-verity as a trust provider
- [RFC PATCH v11 09/19] ipe: add permissive toggle
- [RFC PATCH v11 03/19] ipe: add evaluation loop
- [RFC PATCH v11 08/19] uapi|audit|ipe: add ipe auditing support
- [RFC PATCH v11 16/19] ipe: enable support for fs-verity as a trust provider
- Master key removal semantics
- Re: [RFC PATCH v3 2/9] common/encrypt: add btrfs to get_encryption_*nonce
- Re: [RFC PATCH v3 6/9] tests: adjust generic/429 for extent encryption
- [PATCH 35/35] btrfs: implement process_bio cb for fscrypt
- [PATCH 14/35] btrfs: handle nokey names.
- [PATCH 31/35] btrfs: populate ordered_extent with the orig offset
- [PATCH 23/35] btrfs: populate the ordered_extent with the fscrypt context
- [PATCH 32/35] btrfs: set the bio fscrypt context when applicable
- [PATCH 34/35] btrfs: add orig_logical to btrfs_bio
- [PATCH 12/35] btrfs: add new FEATURE_INCOMPAT_ENCRYPT flag
- [PATCH 17/35] btrfs: add get_devices hook for fscrypt
- [PATCH 10/35] btrfs: start using fscrypt hooks
- [PATCH 28/35] btrfs: pass the fscrypt_info through the replace extent infrastructure
- [PATCH 13/35] btrfs: adapt readdir for encrypted and nokey names
- [PATCH 25/35] btrfs: add an optional encryption context to the end of file extents
- [PATCH 18/35] btrfs: turn on inlinecrypt mount option for encrypt
- [PATCH 15/35] btrfs: implement fscrypt ioctls
- [PATCH 26/35] btrfs: explicitly track file extent length for replace and drop
- [PATCH 24/35] btrfs: keep track of fscrypt info and orig_start for dio reads
- [PATCH 20/35] btrfs: add fscrypt_info and encryption_type to extent_map
- [PATCH 11/35] btrfs: add inode encryption contexts
- [PATCH 22/35] btrfs: plumb through setting the fscrypt_info for ordered extents
- [PATCH 19/35] btrfs: set file extent encryption excplicitly
- [PATCH 21/35] btrfs: add fscrypt_info and encryption_type to ordered_extent
- [PATCH 30/35] btrfs: setup fscrypt_extent_info for new extents
- [PATCH 33/35] btrfs: add a bio argument to btrfs_csum_one_bio
- [PATCH 29/35] btrfs: implement the fscrypt extent encryption hooks
- [PATCH 27/35] btrfs: pass through fscrypt_extent_info to the file extent helpers
- [PATCH 16/35] btrfs: add encryption to CONFIG_BTRFS_DEBUG
- [PATCH 09/35] btrfs: disable verity on encrypted inodes
- [PATCH 08/35] btrfs: disable various operations on encrypted inodes
- [PATCH 07/35] btrfs: add infrastructure for safe em freeing
- [PATCH 06/35] fscrypt: add documentation about extent encryption
- [PATCH 05/35] fscrypt: expose fscrypt_nokey_name
- [PATCH 03/35] fscrypt: disable all but standard v2 policies for extent encryption
- [PATCH 01/35] fscrypt: rename fscrypt_info => fscrypt_inode_info
- [PATCH 02/35] fscrypt: add per-extent encryption support
- [PATCH 04/35] blk-crypto: add a process bio callback
- [PATCH 00/35] btrfs: add fscrypt support
- [PATCH v3 5/5] fscrypt: support crypto data unit size less than filesystem block size
- [PATCH v3 1/5] fscrypt: make it clearer that key_prefix is deprecated
- [PATCH v3 3/5] fscrypt: compute max_lblk_bits from s_maxbytes and block size
- [PATCH v3 2/5] fscrypt: make the bounce page pool opt-in instead of opt-out
- [PATCH v3 0/5] fscrypt: add support for data_unit_size < fs_block_size
- [PATCH v3 4/5] fscrypt: replace get_ino_and_lblk_bits with just has_32bit_inodes
- RE: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [RFC PATCH 0/4] fscrypt: add support for per-extent encryption
- Re: [RFC PATCH 0/4] fscrypt: add support for per-extent encryption
- Re: [PATCH 2/4] fscrypt: add per-extent encryption support
- Re: [PATCH 2/4] fscrypt: add per-extent encryption support
- [PATCH 1/4] fscrypt: rename fscrypt_info => fscrypt_inode_info
- [PATCH 4/4] blk-crypto: add a process bio callback
- [PATCH 3/4] fscrypt: disable all but standard v2 policies for extent encryption
- [PATCH 2/4] fscrypt: add per-extent encryption support
- [RFC PATCH 0/4] fscrypt: add support for per-extent encryption
- [PATCH v2 5/5] fscrypt: support crypto data unit size less than filesystem block size
- [PATCH v2 4/5] fscrypt: replace get_ino_and_lblk_bits with just has_32bit_inodes
- [PATCH v2 3/5] fscrypt: use s_maxbytes instead of filesystem lblk_bits
- [PATCH v2 2/5] fscrypt: make the bounce page pool opt-in instead of opt-out
- [PATCH v2 1/5] fscrypt: make it extra clear that key_prefix is deprecated
- [PATCH v2 0/5] fscrypt: add support for data_unit_size < fs_block_size
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Srinivas Kandagatla
- Re: [RFC PATCH 00/13] fscrypt: add extent encryption
- Re: [RFC PATCH 07/13] fscrypt: store full fscrypt_contexts for each extent
- Re: [RFC PATCH 00/13] fscrypt: add extent encryption
- Re: [PATCH] quota: explicitly forbid quota files from being encrypted
- [PATCH 3/5] fscrypt: use s_maxbytes instead of filesystem lblk_bits
- [PATCH 1/5] fscrypt: make it extra clear that key_prefix is deprecated
- [PATCH 0/5] fscrypt: add support for data_unit_size < fs_block_size
- [PATCH 5/5] fscrypt: support crypto data unit size less than filesystem block size
- [PATCH 4/5] fscrypt: replace get_ino_and_lblk_bits with just has_32bit_inodes
- [PATCH 2/5] fscrypt: make the bounce page pool opt-in instead of opt-out
- [PATCH] quota: explicitly forbid quota files from being encrypted
- [RFC PATCH 13/13] fscrypt: update documentation for per-extent keys
- [RFC PATCH 12/13] fscrypt: allow asynchronous info freeing
- [RFC PATCH 10/13] fscrypt: allow multiple extents to reference one info
- [RFC PATCH 11/13] fscrypt: cache list of inlinecrypt devices
- [RFC PATCH 09/13] fscrypt: revamp key removal for extent encryption
- [RFC PATCH 08/13] fscrypt: save session key credentials for extent infos
- [RFC PATCH 06/13] fscrypt: allow load/save of extent contexts
- [RFC PATCH 07/13] fscrypt: store full fscrypt_contexts for each extent
- [RFC PATCH 04/13] fscrypt: split fscrypt_info into general and inode specific parts
- [RFC PATCH 05/13] fscrypt: add creation/usage/freeing of per-extent infos
- [RFC PATCH 03/13] fscrypt: move function call warning of busy inodes
- [RFC PATCH 02/13] fscrypt: adjust effective lblks based on extents
- [RFC PATCH 01/13] fscrypt: factor getting info for a specific block
- [RFC PATCH 00/13] fscrypt: add extent encryption
- Re: [PATCH v2 04/10] soc: qcom: ice: support for hardware wrapped keys
- Re: [PATCH v2 03/10] soc: qcom: ice: add hwkm support in ice
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Srinivas Kandagatla
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Srinivas Kandagatla
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Srinivas Kandagatla
- Re: [GIT PULL] fscrypt update for 6.6
- Re: [PATCH] KEYS: Include linux/errno.h in linux/verification.h
- [GIT PULL] fscrypt update for 6.6
- Re: [PATCH 2/12] ubifs: Do not include crypto/algapi.h
- [PATCH] KEYS: Include linux/errno.h in linux/verification.h
- Re: [PATCH 2/12] ubifs: Do not include crypto/algapi.h
- Re: [PATCH 3/12] Bluetooth: Do not include crypto/algapi.h
- From: Luiz Augusto von Dentz
- Re: [PATCH 1/12] fscrypt: Do not include crypto/algapi.h
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Srinivas Kandagatla
- Re: [PATCH 9/12] evm: Do not include crypto/algapi.h
- Re: [PATCH 10/12] KEYS: encrypted: Do not include crypto/algapi.h
- Re: [PATCH 6/12] wifi: mac80211: Do not include crypto/algapi.h
- Re: [PATCH 6/12] wifi: mac80211: Do not include crypto/algapi.h
- Re: [PATCH 6/12] wifi: mac80211: Do not include crypto/algapi.h
- Re: [PATCH 4/12] ceph: Do not include crypto/algapi.h
- Re: [PATCH 8/12] SUNRPC: Do not include crypto/algapi.h
- Re: [PATCH 7/12] mptcp: Do not include crypto/algapi.h
- Re: [PATCH 11/12] wireguard: Do not include crypto/algapi.h
- Re: [PATCH 6/12] wifi: mac80211: Do not include crypto/algapi.h
- [PATCH 0/12] Do not include crypto/algapi.h
- Re: [PATCH v4 0/4] crypto: LEA block cipher implementation
- RE: [PATCH v4 0/4] crypto: LEA block cipher implementation
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 09/16] fscrypt: revamp key removal for extent encryption
- Re: [PATCH v3 15/16] fscrypt: allow asynchronous info freeing
- Re: [PATCH v3 14/16] fscrypt: cache list of inlinecrypt devices
- Re: [PATCH v3 12/16] fscrypt: save session key credentials for extent infos
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 13/16] fscrypt: allow multiple extents to reference one info
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- RE: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Gaurav Kashyap (QUIC)
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 13/16] fscrypt: allow multiple extents to reference one info
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v6 8/8] fscrypt: make prepared keys record their type
- Re: [PATCH v6 6/8] fscrypt: move all the shared mode key setup deeper
- Re: [PATCH v6 5/8] fscrypt: reduce special-casing of IV_INO_LBLK_32
- Re: [PATCH v6 3/8] fscrypt: split setup_per_mode_enc_key()
- Re: [PATCH v6 2/8] fscrypt: split and rename setup_file_encryption_key()
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v6 8/8] fscrypt: make prepared keys record their type
- Re: [PATCH v3 00/17] btrfs: add encryption feature
- Re: [PATCH v3 17/17] btrfs: save and load fscrypt extent contexts
- Re: [PATCH v3 08/17] btrfs: handle nokey names.
- Re: [PATCH v3 05/17] btrfs: add inode encryption contexts
- Re: [PATCH v3 00/16] fscrypt: add extent encryption
- Re: [PATCH v3 07/16] fscrypt: use an optional ino equivalent for per-extent infos
- Re: [RFC PATCH v10 11/17] dm-verity: consume root hash digest and signature data via LSM hook
- Re: [PATCH v3 01/16] fscrypt: factor helper for locking master key
- Re: [PATCH v6 8/8] fscrypt: make prepared keys record their type
- Re: [PATCH v6 7/8] fscrypt: make infos have a pointer to prepared keys
- Re: [PATCH v6 6/8] fscrypt: move all the shared mode key setup deeper
- Re: [PATCH v6 4/8] fscrypt: move dirhash key setup away from IO key setup
- Re: [PATCH v6 3/8] fscrypt: split setup_per_mode_enc_key()
- Re: [PATCH v6 1/8] fscrypt: move inline crypt decision to info setup
- Re: [PATCH v6 2/8] fscrypt: split and rename setup_file_encryption_key()
- Re: [PATCH v6 5/8] fscrypt: reduce special-casing of IV_INO_LBLK_32
- Re: [RFC PATCH v10 11/17] dm-verity: consume root hash digest and signature data via LSM hook
- Re: [RFC PATCH v10 11/17] dm-verity: consume root hash digest and signature data via LSM hook
- Re: [RFC PATCH v3 9/9] btrfs: test snapshotting encrypted subvol
- [PATCH v3 01/17] btrfs: disable various operations on encrypted inodes
- [PATCH v3 09/17] btrfs: implement fscrypt ioctls
- [PATCH v3 02/17] btrfs: disable verity on encrypted inodes
- [PATCH v3 00/17] btrfs: add encryption feature
- [PATCH v3 06/17] btrfs: add new FEATURE_INCOMPAT_ENCRYPT flag
- [PATCH v3 05/17] btrfs: add inode encryption contexts
- [PATCH v3 08/17] btrfs: handle nokey names.
- [PATCH v3 04/17] btrfs: start using fscrypt hooks
- [PATCH v3 03/17] fscrypt: expose fscrypt_nokey_name
- [PATCH v3 16/16] fscrypt: update documentation for per-extent keys
- [PATCH v3 14/16] fscrypt: cache list of inlinecrypt devices
- [PATCH v3 15/16] fscrypt: allow asynchronous info freeing
- [PATCH v3 07/17] btrfs: adapt readdir for encrypted and nokey names
- [PATCH v3 13/16] fscrypt: allow multiple extents to reference one info
- [PATCH v3 12/16] fscrypt: save session key credentials for extent infos
- [PATCH v3 11/16] fscrypt: allow load/save of extent contexts
- [PATCH v6 5/8] fscrypt: reduce special-casing of IV_INO_LBLK_32
- [PATCH v6 6/8] fscrypt: move all the shared mode key setup deeper
- [PATCH v6 4/8] fscrypt: move dirhash key setup away from IO key setup
- [PATCH v6 3/8] fscrypt: split setup_per_mode_enc_key()
- [PATCH v6 2/8] fscrypt: split and rename setup_file_encryption_key()
- [PATCH v6 8/8] fscrypt: make prepared keys record their type
- [PATCH v6 1/8] fscrypt: move inline crypt decision to info setup
- [PATCH v6 7/8] fscrypt: make infos have a pointer to prepared keys
- [RFC PATCH v3 9/9] btrfs: test snapshotting encrypted subvol
- [RFC PATCH v3 6/9] tests: adjust generic/429 for extent encryption
- [RFC PATCH v3 5/9] generic/613: write some actual data for btrfs
- [RFC PATCH v3 4/9] common/encrypt: enable making a encrypted btrfs filesystem
- [RFC PATCH v3 3/9] common/encrypt: add btrfs to get_ciphertext_filename
- [RFC PATCH v3 7/9] common/verity: explicitly don't allow btrfs encryption
- [RFC PATCH v3 2/9] common/encrypt: add btrfs to get_encryption_*nonce
- [RFC PATCH v3 1/9] common/encrypt: separate data and inode nonces
- [RFC PATCH v3 0/9] fstests: add btrfs encryption testing
- [RFC PATCH v3 8/9] btrfs: add simple test of reflink of encrypted data
- [PATCH v3 12/17] btrfs: turn on inlinecrypt mount option for encrypt
- [PATCH v3 11/17] btrfs: add get_devices hook for fscrypt
- [PATCH v3 10/17] btrfs: add encryption to CONFIG_BTRFS_DEBUG
- [PATCH v3 17/17] btrfs: save and load fscrypt extent contexts
- [PATCH v3 16/17] btrfs: explicitly track file extent length and encryption
- [PATCH v3 15/17] btrfs: start tracking extent encryption context info
- [PATCH v3 14/17] btrfs: create and free extent fscrypt_infos
- [PATCH v3 13/17] btrfs: turn on the encryption ioctls
- [PATCH v3 05/16] fscrypt: setup leaf inodes for extent encryption
- [PATCH v3 09/16] fscrypt: revamp key removal for extent encryption
- [PATCH v3 06/16] fscrypt: allow infos to be owned by extents
- [PATCH v3 08/16] fscrypt: move function call warning of busy inodes
- [PATCH v3 07/16] fscrypt: use an optional ino equivalent for per-extent infos
- [PATCH v3 10/16] fscrypt: add creation/usage/freeing of per-extent infos
- [PATCH v3 03/16] fscrypt: adjust effective lblks based on extents
- [PATCH v3 04/16] fscrypt: add a super_block pointer to fscrypt_info
- [PATCH v3 02/16] fscrypt: factor getting info for a specific block
- [PATCH v3 01/16] fscrypt: factor helper for locking master key
- [PATCH v3 00/16] fscrypt: add extent encryption
- [PATCH v6 0/8] fscrypt: preliminary rearrangmeents of key setup
- Re: [PATCH RFC v10 7/17] ipe: add userspace interface
- Re: [PATCH RFC v10 8/17] uapi|audit|ipe: add ipe auditing support
- RE: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- From: Gaurav Kashyap (QUIC)
- Re: [RFC PATCH v10 11/17] dm-verity: consume root hash digest and signature data via LSM hook
- Re: [PATCH v5 8/8] fscrypt: make prepared keys record their type
- Re: [PATCH v2 07/10] qcom_scm: scm call for create, prepare and import keys
- Re: [PATCH v2 02/10] qcom_scm: scm call for deriving a software secret
- Re: [PATCH v2 02/10] qcom_scm: scm call for deriving a software secret
- Re: [PATCH v2 07/10] qcom_scm: scm call for create, prepare and import keys
- Re: [PATCH v2 09/10] soc: qcom: support for generate, import and prepare key
- Re: [PATCH v2 02/10] qcom_scm: scm call for deriving a software secret
- Re: [PATCH v2 07/10] qcom_scm: scm call for create, prepare and import keys
- Re: [PATCH v2 00/10] Hardware wrapped key support for qcom ice and ufs
- Re: [PATCH v2 07/10] qcom_scm: scm call for create, prepare and import keys
- [PATCH v2 09/10] soc: qcom: support for generate, import and prepare key
- [PATCH v2 10/10] ufs: host: support for generate, import and prepare key
- [PATCH v2 08/10] ufs: core: add support for generate, import and prepare keys
[Index of Archives]
[linux Cryptography]
[Asterisk App Development]
[PJ SIP]
[Gnu Gatekeeper]
[Linux Kernel]
[Fedora Users]
[Yosemite Campsites]