Files
linux/fs
Eric Biggers 73b321a1d2 UPSTREAM: fscrypt: restrict IV_INO_LBLK_* to AES-256-XTS
IV_INO_LBLK_* exist only because of hardware limitations, and currently
the only known use case for them involves AES-256-XTS.  Therefore, for
now only allow them in combination with AES-256-XTS.  This way we don't
have to worry about them being combined with other encryption modes.

(To be clear, combining IV_INO_LBLK_* with other encryption modes
*should* work just fine.  It's just not being tested, so we can't be
100% sure it works.  So with no known use case, it's best to disallow it
for now, just like we don't allow other weird combinations like
AES-256-XTS contents encryption with Adiantum filenames encryption.)

This can be relaxed later if a use case for other combinations arises.

Fixes: b103fb7653 ("fscrypt: add support for IV_INO_LBLK_64 policies")
Fixes: e3b1078bed ("fscrypt: add support for IV_INO_LBLK_32 policies")
Link: https://lore.kernel.org/r/20200721181012.39308-1-ebiggers@kernel.org
Signed-off-by: Eric Biggers <ebiggers@google.com>
(cherry picked from commit f000223c98)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
Change-Id: I243e2c3de549e322a311610fa565ffe87990c8e9
2020-11-15 15:06:09 +01:00
..
2020-11-05 11:08:53 +01:00
2020-11-05 11:08:44 +01:00
2019-08-06 19:06:51 +02:00
2020-10-30 10:38:28 +01:00
2018-08-17 16:20:28 -07:00
2019-05-22 08:00:39 +02:00
2019-12-13 08:51:59 +01:00
2020-11-05 11:08:50 +01:00
2020-06-22 09:05:01 +02:00
2020-03-05 16:42:12 +01:00
2020-04-29 17:26:17 +02:00
2020-05-03 08:48:02 +02:00
2020-01-04 19:29:03 +01:00