linux/fs/crypto
Eric Biggers 231baecdef crypto: clarify name of WEAK_KEY request flag
CRYPTO_TFM_REQ_WEAK_KEY confuses newcomers to the crypto API because it
sounds like it is requesting a weak key.  Actually, it is requesting
that weak keys be forbidden (for algorithms that have the notion of
"weak keys"; currently only DES and XTS do).

Also it is only one letter away from CRYPTO_TFM_RES_WEAK_KEY, with which
it can be easily confused.  (This in fact happened in the UX500 driver,
though just in some debugging messages.)

Therefore, make the intent clear by renaming it to
CRYPTO_TFM_REQ_FORBID_WEAK_KEYS.

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
2019-01-25 18:41:52 +08:00
..
bio.c fscrypt: allow synchronous bio decryption 2018-05-02 14:30:57 -07:00
crypto.c fscrypt: add Adiantum support 2019-01-06 08:36:21 -05:00
fname.c fscrypt: add Adiantum support 2019-01-06 08:36:21 -05:00
fscrypt_private.h fscrypt: add Adiantum support 2019-01-06 08:36:21 -05:00
hooks.c fscrypt: use a common logging function 2018-05-20 16:21:05 -04:00
Kconfig fscrypt: add support for AES-128-CBC 2017-06-23 20:05:07 -04:00
keyinfo.c crypto: clarify name of WEAK_KEY request flag 2019-01-25 18:41:52 +08:00
Makefile fscrypt: new helper function - fscrypt_file_open() 2017-10-18 19:52:37 -04:00
policy.c fscrypt: add Adiantum support 2019-01-06 08:36:21 -05:00