From: Andreas Dilger <adilger@dilger.ca>
To: Daniel Rosenberg <drosen@google.com>
Cc: "Theodore Y . Ts'o" <tytso@mit.edu>,
Eric Biggers <ebiggers@kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Gabriel Krisman Bertazi <krisman@collabora.com>,
kernel-team@android.com
Subject: Re: [PATCH v2 1/2] ext4: Handle casefolding with encryption
Date: Sat, 20 Mar 2021 03:05:54 -0600 [thread overview]
Message-ID: <0399B7C7-D6A1-4A92-ABDD-1EA13C80007E@dilger.ca> (raw)
In-Reply-To: <20210319073414.1381041-2-drosen@google.com>
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
On Mar 19, 2021, at 1:34 AM, Daniel Rosenberg <drosen@google.com> wrote:
>
> This adds support for encryption with casefolding.
>
> Since the name on disk is case preserving, and also encrypted, we can no
> longer just recompute the hash on the fly. Additionally, to avoid
> leaking extra information from the hash of the unencrypted name, we use
> siphash via an fscrypt v2 policy.
>
> The hash is stored at the end of the directory entry for all entries
> inside of an encrypted and casefolded directory apart from those that
> deal with '.' and '..'. This way, the change is backwards compatible
> with existing ext4 filesystems.
>
> Signed-off-by: Daniel Rosenberg <drosen@google.com>
Reviewed-by: Andreas Dilger <adilger@dilger.ca>
Cheers, Andreas
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
next prev parent reply other threads:[~2021-03-20 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 7:34 [PATCH v2 0/2] Reconcile Encryption and Casefolding in Ext4 Daniel Rosenberg
2021-03-19 7:34 ` [PATCH v2 1/2] ext4: Handle casefolding with encryption Daniel Rosenberg
2021-03-20 9:05 ` Andreas Dilger [this message]
2021-04-06 2:38 ` Theodore Ts'o
2021-03-19 7:34 ` [PATCH v2 2/2] ext4: Optimize match for casefolded encrypted dirs Daniel Rosenberg
2021-04-06 2:38 ` 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=0399B7C7-D6A1-4A92-ABDD-1EA13C80007E@dilger.ca \
--to=adilger@dilger.ca \
--cc=drosen@google.com \
--cc=ebiggers@kernel.org \
--cc=kernel-team@android.com \
--cc=krisman@collabora.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).