Thread (3 messages) flat view 3 messages, 3 authors, 2016-09-15

Re: fscrypto: improved validation when loading inode encryption metadata

From: Theodore Ts'o <tytso@mit.edu>
Date: 2016-09-15 20:17:44
Also in: linux-f2fs-devel, linux-fsdevel

On Mon, Sep 12, 2016 at 12:24:00PM -0700, Eric Biggers wrote:
- Validate fscrypt_context.format and fscrypt_context.flags.  If
  unrecognized values are set, then the kernel may not know how to
  interpret the encrypted file, so it should fail the operation.

- Validate that AES_256_XTS is used for contents and that AES_256_CTS is
  used for filenames.  It was previously possible for the kernel to
  accept these reversed, though it would have taken manual editing of
  the block device.  This was not intended.

- Fail cleanly rather than BUG()-ing if a file has an unexpected type.

Signed-off-by: Eric Biggers <redacted>
Thanks, applied.  (I plan to carry Eric's fscrypto changes ext4 git
tree; Jaeguk, I assume you have no objections?)

		   	       	       	   	- Ted
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help