From: Eric Biggers <ebiggers@google.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
Theodore Ts'o <tytso@mit.edu>,
jaegeuk@kernel.org
Subject: Re: [PATCH] fscrypto: make XTS tweak initialization endian-independent
Date: Mon, 3 Oct 2016 11:03:40 -0700 [thread overview]
Message-ID: <20161003180340.GA54410@google.com> (raw)
In-Reply-To: <CAFLxGvyCHwWms8wJf1gU0hRj__Q0Z2F2wKuZ3sYNfp8wQ9S4PQ@mail.gmail.com>
On Sat, Oct 01, 2016 at 06:03:31PM +0200, Richard Weinberger wrote:
> Eric,
>
> On Fri, Sep 30, 2016 at 7:58 PM, Eric Biggers <ebiggers@google.com> wrote:
> > The XTS tweak (or IV) was initialized differently on little endian and
> > big endian systems. Because the ciphertext depends on the XTS tweak, it
> > was not possible to use an encrypted filesystem created by a little
> > endian system on a big endian system and vice versa, even if they shared
> > the same PAGE_SIZE. Fix this by always using little endian.
> >
> > This will break hypothetical big endian users of ext4 or f2fs
> > encryption. However, all users we are aware of are little endian, and
> > it's believed that "real" big endian users are unlikely to exist yet.
> > So this might as well be fixed now before it's too late.
> >
> > Signed-off-by: Eric Biggers <ebiggers@google.com>
> > ---
> > fs/crypto/crypto.c | 15 ++++++++-------
> > 1 file changed, 8 insertions(+), 7 deletions(-)
> >
> > diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
> > index 61057b7d..98f87fe 100644
> > --- a/fs/crypto/crypto.c
> > +++ b/fs/crypto/crypto.c
> > @@ -151,7 +151,10 @@ static int do_page_crypto(struct inode *inode,
> > struct page *src_page, struct page *dest_page,
> > gfp_t gfp_flags)
> > {
> > - u8 xts_tweak[FS_XTS_TWEAK_SIZE];
> > + struct {
> > + __le64 index;
> > + u8 padding[FS_XTS_TWEAK_SIZE - sizeof(__le64)];
> > + } xts_tweak;
>
> While we are here, wouldn't it make sense to rename the variable to "iv"?
> In aes-xts mode the IV is used as tweak. But it is still an IV and passed
> as IV parameter to the crypto API.
>
> Especially when other cipher modes are used this is confusing.
>
Good idea --- I agree that "iv" is a better name, so as to not tie the code to
XTS specifically. But I think the renaming should be a separate patch.
Also, currently this code *is* only supposed to be used for XTS. There's a bug
where a specially crafted filesystem can cause this code path to be entered with
CTS, but I have a patch pending in the ext4 tree to fix that.
Eric
next prev parent reply other threads:[~2016-10-03 18:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 17:58 [PATCH] fscrypto: make XTS tweak initialization endian-independent Eric Biggers
2016-09-30 17:58 ` Eric Biggers
2016-10-01 16:03 ` Richard Weinberger
2016-10-03 18:03 ` Eric Biggers [this message]
2016-10-04 8:46 ` Richard Weinberger
2016-10-04 16:38 ` Eric Biggers
2016-10-05 9:08 ` David Gstir
2016-10-13 3:39 ` Theodore Ts'o
2016-10-13 3:39 ` Theodore Ts'o
[not found] <20161005170659.GA110549@google.com>
2016-10-05 18:23 ` Michael Halcrow
2016-10-05 18:44 ` Richard Weinberger
2016-10-05 21:11 ` Michael Halcrow
2016-10-05 21:18 ` Richard Weinberger
2016-10-05 21:14 ` Richard Weinberger
2016-10-06 1:17 ` Dave Chinner
2016-10-06 2:16 ` Theodore Ts'o
2016-10-06 22:23 ` Dave Chinner
2016-10-07 16:05 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161003180340.GA54410@google.com \
--to=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.