From: Eric Biggers <ebiggers@kernel.org>
To: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-fscrypt@vger.kernel.org, linux-btrfs@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH v3 04/22] fscrypt: add extent-based encryption
Date: Thu, 20 Oct 2022 16:56:31 -0700 [thread overview]
Message-ID: <Y1HgL+2e/r6H0D45@sol.localdomain> (raw)
In-Reply-To: <43955182-7158-0ce9-aeff-7dfa51559624@dorminy.me>
On Thu, Oct 20, 2022 at 06:55:04PM -0400, Sweet Tea Dorminy wrote:
>
>
> On 10/20/22 17:45, Eric Biggers wrote:
> > On Thu, Oct 20, 2022 at 12:58:23PM -0400, Sweet Tea Dorminy wrote:
> > > Some filesystems need to encrypt data based on extents, rather than on
> > > inodes, due to features incompatible with inode-based encryption. For
> > > instance, btrfs can have multiple inodes referencing a single block of
> > > data, and moves logical data blocks to different physical locations on
> > > disk in the background; these two features mean traditional inode-based
> > > file contents encryption will not work for btrfs.
> > >
> > > This change introduces fscrypt_extent_context objects, in analogy to
> > > existing context objects based on inodes. For a filesystem which opts to
> > > use extent-based encryption, a new hook provides a new
> > > fscrypt_extent_context, generated in close analogy to the IVs generated
> > > with existing policies. During file content encryption/decryption, the
> > > existing fscrypt_context object provides key information, while the new
> > > fscrypt_extent_context provides IV information. For filename encryption,
> > > the existing IV generation methods are still used, since filenames are
> > > not stored in extents.
> > >
> > > Signed-off-by: Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
> > > ---
> > > fs/crypto/crypto.c | 20 ++++++++--
> > > fs/crypto/fscrypt_private.h | 25 +++++++++++-
> > > fs/crypto/inline_crypt.c | 28 ++++++++++---
> > > fs/crypto/policy.c | 79 +++++++++++++++++++++++++++++++++++++
> > > include/linux/fscrypt.h | 47 ++++++++++++++++++++++
> > > 5 files changed, 189 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/fs/crypto/crypto.c b/fs/crypto/crypto.c
> > > index 7fe5979fbea2..08b495dc5c0c 100644
> > > --- a/fs/crypto/crypto.c
> > > +++ b/fs/crypto/crypto.c
> > > @@ -81,8 +81,22 @@ void fscrypt_generate_iv(union fscrypt_iv *iv, u64 lblk_num,
> > > const struct fscrypt_info *ci)
> > > {
> > > u8 flags = fscrypt_policy_flags(&ci->ci_policy);
> > > + struct inode *inode = ci->ci_inode;
> > > + const struct fscrypt_operations *s_cop = inode->i_sb->s_cop;
> > > - memset(iv, 0, ci->ci_mode->ivsize);
> > > + memset(iv, 0, sizeof(*iv));
> > > + if (s_cop->get_extent_context && lblk_num != U64_MAX) {
> > > + size_t extent_offset;
> > > + union fscrypt_extent_context ctx;
> > > + int ret;
> > > +
> > > + ret = fscrypt_get_extent_context(inode, lblk_num, &ctx,
> > > + &extent_offset, NULL);
> > > + WARN_ON_ONCE(ret);
> > > + memcpy(iv->raw, ctx.v1.iv.raw, sizeof(*iv));
> > > + iv->lblk_num += cpu_to_le64(extent_offset);
> > > + return;
> > > + }
> >
> > Please read through my review comment
> > https://lore.kernel.org/linux-fscrypt/Yx6MnaUqUTdjCmX+@quark/ again, as it
> > doesn't seem that you've addressed it.
> >
> > - Eric
>
> I probably didn't understand it correctly. I think there were three points
> in it:
>
> 1) reconsider per-extent keys
> 2) make IV generation work for non-directkey policies as similarly as
> possible to how they work in inode-based filesystems
> 3) never use 'file-based' except in contrast to dm-crypt and other
> block-layer encryption.
>
> For point 2, I changed the initial extent context generation to match up
> with fscrypt_generate_iv() (and probably didn't call that out enough in the
> description). (Looking at it again, I could literally call
> fscrypt_generate_iv() to generate the initial extent context; I didn't
> realize that before).
>
> Then adding lblk_num to the existing lblk_num in the iv from the start of
> the extent should be the same as the iv->lblk_num setting in the inode-based
> case: for lblk 12, for instance, the same IV should result from inode-based
> with lblk 12, as with extent-based with an initial lblk_num of 9 and an
> extent_offset of 3. For shared extents, they'll be different, but for
> singly-referenced extents, the IVs should be exactly the same in theory.
>
> I'm not sure whether I misunderstood the points or didn't address them
> fully, I apologize. Would you be up for elaborating where I missed, either
> by email or by videochat whenever works for you?
It seems you misunderstood point (2). See what I said below:
So if you do want to implement the DIRECT_KEY method, the natural thing
to do would be to store a 16-byte nonce along with each extent, and use
the DIRECT_KEY IV generation method as-is. It seems that you've done it
a bit differently; you store a 32-byte nonce and generate the IV as
'nonce + lblk_num', instead of 'nonce || lblk_num'. I think that's a
mistake -- it should be exactly the same.
If the issue is that the 'nonce || lblk_num' method doesn't allow for
AES-XTS support, we could extend DIRECT_KEY to do 'nonce + lblk_num'
*if* the algorithm has a 16-byte IV size and thus has to tolerate some
chance of IV reuse. Note that this change would be unrelated to
extent-based encryption, and could be applied regardless of it.
So:
1.) Provided that you've decided against per-extent keys, and are not trying to
support UFS and eMMC inline encryption hardware, then you should *only*
support DIRECT_KEY -- not other settings that don't make sense.
2.) There should be a preparatory patch that makes DIRECT_KEY be allowed when
the IV length is 16 bytes, using the method 'nonce + lblk_num' -- assuming
that you need AES-XTS support and aren't planning on supporting Adiantum or
AES-HCTR2 only. (The small chance for IV reuse that it results in is not
ideal, but it's probably tolerable. Maybe the nonce should also be hashed
with a secret key, like what IV_INO_LBLK_32 does with the inode number; I'll
have to think about it.) If you plan to just support AES-HCTR2 instead of
AES-XTS, then you'd need a patch to allow AES-HCTR2 for contents encryption,
as currently it is only allowed for filenames.
3.) Each extent context should contain a 16-byte random nonce, that is newly
generated just for that extent -- not copied from anywhere.
4.) IVs should be generated using the DIRECT_KEY method. That is,
'nonce || lblk_num' if the IV length allows it, otherwise 'nonce + lblk_num'
as mentioned in (2). For inode-based encryption, nonce means the inode's
nonce, and lblk_num means the index of the block in the inode. For
extent-based encryption, nonce will mean the extent's nonce, and lblk_num
will mean the index of the block in the extent.
- Eric
next prev parent reply other threads:[~2022-10-20 23:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 16:58 [PATCH v3 00/22] btrfs: add fscrypt integration Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 01/22] fscrypt: expose fscrypt_nokey_name Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 02/22] fscrypt: add fscrypt_have_same_policy() to check inode compatibility Sweet Tea Dorminy
2022-10-20 20:52 ` Josef Bacik
2022-10-20 16:58 ` [PATCH v3 03/22] fscrypt: allow fscrypt_generate_iv() to distinguish filenames Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 04/22] fscrypt: add extent-based encryption Sweet Tea Dorminy
2022-10-20 21:40 ` Eric Biggers
2022-10-20 22:20 ` Sweet Tea Dorminy
2022-10-20 21:45 ` Eric Biggers
2022-10-20 22:55 ` Sweet Tea Dorminy
2022-10-20 23:56 ` Eric Biggers [this message]
2022-10-21 0:37 ` Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 05/22] fscrypt: document btrfs' fscrypt quirks Sweet Tea Dorminy
2022-10-20 21:41 ` Eric Biggers
2022-10-20 22:07 ` Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 06/22] btrfs: use struct qstr instead of name and namelen Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 07/22] btrfs: setup qstrings from dentrys using fscrypt helper Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 08/22] btrfs: use struct fscrypt_str instead of struct qstr Sweet Tea Dorminy
2022-10-21 20:42 ` Josef Bacik
2022-10-20 16:58 ` [PATCH v3 09/22] btrfs: store directory encryption state Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 10/22] btrfs: disable various operations on encrypted inodes Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 11/22] btrfs: start using fscrypt hooks Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 12/22] btrfs: add fscrypt_context items Sweet Tea Dorminy
2022-10-21 20:54 ` Josef Bacik
2022-10-20 16:58 ` [PATCH v3 13/22] btrfs: translate btrfs encryption flags and encrypted inode flag Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 14/22] btrfs: store a fscrypt extent context per normal file extent Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 15/22] btrfs: encrypt normal file extent data if appropriate Sweet Tea Dorminy
2022-10-21 20:58 ` Josef Bacik
2022-10-20 16:58 ` [PATCH v3 16/22] btrfs: Add new FEATURE_INCOMPAT_ENCRYPT feature flag Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 17/22] btrfs: implement fscrypt ioctls Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 18/22] btrfs: permit searching for nokey names for removal Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 19/22] btrfs: use correct name hash for nokey names Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 20/22] btrfs: adapt lookup for partially encrypted directories Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 21/22] fscrypt: add flag allowing partially-encrypted directories Sweet Tea Dorminy
2022-10-20 16:58 ` [PATCH v3 22/22] btrfs: encrypt verity items Sweet Tea Dorminy
2022-10-20 21:38 ` [PATCH v3 00/22] btrfs: add fscrypt integration Eric Biggers
2022-10-20 23:12 ` David Sterba
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=Y1HgL+2e/r6H0D45@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jaegeuk@kernel.org \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fscrypt@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).