Eric Biggers 6f99756dab fscrypt: zeroize fscrypt_info before freeing ... memset the struct fscrypt_info to zero before freeing. This isn't really needed currently, since there's no secret key directly in the fscrypt_info. But there's a decent chance that someone will add such a field in the future, e.g. in order to use an API that takes a raw key such as siphash(). So it's good to do this as a hardening measure. Signed-off-by: Eric Biggers <ebiggers@google.com>		2019-10-21 13:22:08 -07:00
..
bio.c	fscrypt: remove struct fscrypt_ctx	2019-10-21 13:22:08 -07:00
crypto.c	fscrypt: remove struct fscrypt_ctx	2019-10-21 13:22:08 -07:00
fname.c	fscrypt: v2 encryption policy support	2019-08-12 19:18:50 -07:00
fscrypt_private.h	fscrypt: remove struct fscrypt_ctx	2019-10-21 13:22:08 -07:00
hkdf.c	fscrypt: add an HKDF-SHA512 implementation	2019-08-12 19:18:50 -07:00
hooks.c	fscrypt: make fscrypt_msg() take inode instead of super_block	2019-08-12 19:04:44 -07:00
Kconfig	fscrypt: add an HKDF-SHA512 implementation	2019-08-12 19:18:50 -07:00
keyring.c	fscrypt: require that key be added when setting a v2 encryption policy	2019-08-12 19:18:50 -07:00
keysetup.c	fscrypt: zeroize fscrypt_info before freeing	2019-10-21 13:22:08 -07:00
keysetup_v1.c	fscrypt: invoke crypto API for ESSIV handling	2019-10-21 13:22:08 -07:00
Makefile	fscrypt: add an HKDF-SHA512 implementation	2019-08-12 19:18:50 -07:00
policy.c	fscrypt: require that key be added when setting a v2 encryption policy	2019-08-12 19:18:50 -07:00