From: Nathan Huckleberry <nhuck@google.com>
To: fstests@vger.kernel.org
Cc: Eric Biggers <ebiggers@kernel.org>,
Sami Tolvanen <samitolvanen@google.com>,
Nathan Huckleberry <nhuck@google.com>
Subject: [RFC PATCH v3 0/2] generic: test HCTR2 filename encryption
Date: Fri, 20 May 2022 13:23:13 -0500 [thread overview]
Message-ID: <20220520182315.615327-1-nhuck@google.com> (raw)
This patchset is not intended to be accepted yet. It is reliant on HCTR2
support in the kernel which has not yet been accepted. See the HCTR2 patchset
here: https://lore.kernel.org/all/20220520181501.2159644-1-nhuck@google.com/
HCTR2 is a new wide-block encryption mode that can used for filename encryption
in fscrypt. This patchset adds a reference implementation of HCTR2 to the
fscrypt testing utility and adds tests for filename encryption with HCTR2.
More information on HCTR2 can be found here: "Length-preserving encryption with
HCTR2": https://ia.cr/2021/1441
Changes in v3:
* Consolidate tests into one file
Changes in v2:
* Use POLYVAL multiplication directly instead of using GHASH trick
* Split reference implementation and tests into two patches
* Remove v1 policy tests
* Various small style fixes
Nathan Huckleberry (2):
fscrypt-crypt-util: add HCTR2 reference implementation
generic: add tests for fscrypt policies with HCTR2
common/encrypt | 2 +
src/fscrypt-crypt-util.c | 338 ++++++++++++++++++++++++++++++++-------
tests/generic/900 | 28 ++++
tests/generic/900.out | 16 ++
4 files changed, 327 insertions(+), 57 deletions(-)
create mode 100755 tests/generic/900
create mode 100644 tests/generic/900.out
--
2.36.1.124.g0e6072fb45-goog
next reply other threads:[~2022-05-20 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 18:23 Nathan Huckleberry [this message]
2022-05-20 18:23 ` [RFC PATCH v3 1/2] fscrypt-crypt-util: add HCTR2 reference implementation Nathan Huckleberry
2022-05-30 18:17 ` Eric Biggers
2022-05-20 18:23 ` [RFC PATCH v3 2/2] generic: add tests for fscrypt policies with HCTR2 Nathan Huckleberry
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=20220520182315.615327-1-nhuck@google.com \
--to=nhuck@google.com \
--cc=ebiggers@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=samitolvanen@google.com \
/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