messages from 2018-11-17 08:07:00 to 2019-02-12 00:03:57 UTC [more...]
[f2fs-dev] [RFC PATCH v2 00/20] fscrypt: key management improvements
2019-02-12 0:03 UTC (24+ messages)
` [f2fs-dev] [RFC PATCH v2 01/20] fs, fscrypt: move uapi definitions to new header <linux/fscrypt.h>
` [f2fs-dev] [RFC PATCH v2 02/20] fscrypt: use FSCRYPT_ prefix for uapi constants
` [f2fs-dev] [RFC PATCH v2 03/20] fscrypt: use FSCRYPT_* definitions, not FS_*
` [f2fs-dev] [RFC PATCH v2 04/20] fs: add ->s_master_keys to struct super_block
` [f2fs-dev] [RFC PATCH v2 05/20] fscrypt: add ->ci_inode to fscrypt_info
` [f2fs-dev] [RFC PATCH v2 06/20] fscrypt: refactor v1 policy key setup into keysetup_legacy.c
` [f2fs-dev] [RFC PATCH v2 07/20] fscrypt: add FS_IOC_ADD_ENCRYPTION_KEY ioctl
` [f2fs-dev] [RFC PATCH v2 08/20] fs/inode.c: export inode_lru_list_del()
` [f2fs-dev] [RFC PATCH v2 09/20] fs/inode.c: rename and export dispose_list()
` [f2fs-dev] [RFC PATCH v2 10/20] fs/dcache.c: add shrink_dcache_inode()
` [f2fs-dev] [RFC PATCH v2 11/20] fscrypt: add FS_IOC_REMOVE_ENCRYPTION_KEY ioctl
` "
` [f2fs-dev] [RFC PATCH v2 12/20] fscrypt: add FS_IOC_GET_ENCRYPTION_KEY_STATUS ioctl
` [f2fs-dev] [RFC PATCH v2 13/20] fscrypt: add an HKDF-SHA512 implementation
` [f2fs-dev] [RFC PATCH v2 14/20] fscrypt: v2 encryption policy support
` [f2fs-dev] [RFC PATCH v2 15/20] fscrypt: allow unprivileged users to add/remove keys for v2 policies
` [f2fs-dev] [RFC PATCH v2 16/20] fscrypt: require that key be added when setting a v2 encryption policy
` [f2fs-dev] [RFC PATCH v2 17/20] ext4: wire up new fscrypt ioctls
` [f2fs-dev] [RFC PATCH v2 18/20] f2fs: "
` [f2fs-dev] [RFC PATCH v2 19/20] ubifs: "
` [f2fs-dev] [RFC PATCH v2 20/20] fscrypt: document the new ioctls and policy version
Proposal: Yet another possible fs-verity interface
2019-02-10 14:06 UTC (5+ messages)
[PATCH] KEYS: user: Align the payload buffer
2019-02-07 23:35 UTC (3+ messages)
Proposal: A new fs-verity interface
2019-01-29 15:48 UTC (10+ messages)
` [f2fs-dev] "
Transparent encryption mechanism
2019-01-27 19:44 UTC
[PATCH] MAINTAINER: add Eric Biggers as an fscrypt maintainer
2019-01-24 23:51 UTC (2+ messages)
[f2fs-dev] [PATCH] fscrypt: return -EXDEV for incompatible rename or link into encrypted dir
2019-01-23 0:21 UTC
Bug report: unaligned access with ext4 encryption
2019-01-10 23:35 UTC (6+ messages)
[GIT PULL] fscrypt update for 4.21
2019-01-06 21:35 UTC (5+ messages)
[f2fs-dev] [PATCH v2 00/12] fs-verity: read-only file-based authenticity protection
2019-01-04 20:41 UTC (37+ messages)
` [f2fs-dev] [PATCH v2 01/12] fs-verity: add a documentation file
` "
[GIT PULL] fsverity for 4.21-rc
2019-01-03 15:31 UTC
[PATCH 0/7] xfstests: add fs-verity tests
2018-12-15 14:42 UTC (16+ messages)
` [PATCH 1/7] common/verity: add common functions for testing fs-verity
` [PATCH 2/7] generic: test general behavior of verity files
` [PATCH 3/7] generic: test access controls on the fs-verity ioctls
` [PATCH 4/7] generic: test fs-verity descriptor validation
` [PATCH 5/7] generic: test corrupting verity files
` [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
[BUG BISECT next] Files cannot be opened after "fsverity: Move verity status check to fsverity_file_open"
2018-12-12 4:11 UTC (6+ messages)
` [f2fs-dev] "
[PATCH 0/2] fs-verity: fix !CONFIG_FS_VERITY case
2018-12-12 4:07 UTC (7+ messages)
` [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] fscrypt: remove CRYPTO_CTR dependency
2018-12-12 2:40 UTC (4+ messages)
[PATCH v4] fscrypt: add Adiantum support
2018-12-09 21:56 UTC (2+ messages)
[PATCH -next] fsverity: fix Documentation typo
2018-12-05 1:24 UTC
[PATCH v4 00/14] crypto: Adiantum support
2018-11-30 17:58 UTC (15+ messages)
` [PATCH v4 01/14] crypto: chacha20-generic - add HChaCha20 library function
` [PATCH v4 02/14] crypto: chacha20-generic - don't unnecessarily use atomic walk
` [PATCH v4 04/14] crypto: chacha20-generic - refactor to allow varying number of rounds
` [PATCH v4 05/14] crypto: chacha - add XChaCha12 support
` [PATCH v4 07/14] crypto: arm/chacha20 - add XChaCha20 support
` [PATCH v4 08/14] crypto: arm/chacha20 - refactor to allow varying number of rounds
` [PATCH v4 09/14] crypto: arm/chacha - add XChaCha12 support
` [PATCH v4 10/14] crypto: poly1305 - use structures for key and accumulator
` [PATCH v4 11/14] crypto: poly1305 - add Poly1305 core API
` [PATCH v4 12/14] crypto: nhpoly1305 - add NHPoly1305 support
` [PATCH v4 13/14] crypto: arm/nhpoly1305 - add NEON-accelerated NHPoly1305
` [PATCH v4 14/14] crypto: adiantum - add Adiantum support
[PATCH 0/7] Remove fs specific fscrypt and fsverity build config options
2018-11-30 17:44 UTC (31+ messages)
` [PATCH 1/7] ext4: use IS_ENCRYPTED() to check encryption status
` [PATCH 2/7] f2fs: "
` [f2fs-dev] "
` [PATCH 3/7] fscrypt: Remove filesystem specific build config option
` [PATCH 4/7] Add S_VERITY and IS_VERITY()
` [PATCH 5/7] ext4: use IS_VERITY() to check inode's fsverity status
` [PATCH 6/7] f2fs: "
` [f2fs-dev] "
` [PATCH 7/7] fsverity: Remove filesystem specific build config option
[RFC PATCH v3 00/15] crypto: Adiantum support
2018-11-21 7:55 UTC (28+ messages)
` [RFC PATCH v3 10/15] crypto: poly1305 - use structures for key and accumulator
` [RFC PATCH] zinc chacha20 generic implementation using crypto API code
` [RFC PATCH v2 0/4] Exporting existing crypto API code through zinc
` [v2 PATCH 1/4] crypto: chacha20 - Export chacha20 functions without crypto API
` [v2 PATCH 2/4] zinc: ChaCha20 generic C implementation and selftest
` [v2 PATCH 3/4] zinc: Add x86 accelerated ChaCha20
` [v2 PATCH 4/4] zinc: ChaCha20 x86_64 implementation
[RFC PATCH v2 00/12] crypto: Adiantum support
2018-11-19 20:30 UTC (9+ messages)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).