From: Eric Biggers <ebiggers@kernel.org>
To: Simo Sorce <simo@redhat.com>
Cc: Thibaud Ecarot <thibaud.ecarot@gmail.com>,
Jeff Layton <jlayton@redhat.com>,
linux-fscrypt <linux-fscrypt@vger.kernel.org>
Subject: Re: fscrypt and FIPS
Date: Tue, 16 Feb 2021 11:04:43 -0800 [thread overview]
Message-ID: <YCwXSwseAoMdkXGG@gmail.com> (raw)
In-Reply-To: <29e4defba658cae99faccef451d7873b4cc056d9.camel@redhat.com>
On Tue, Feb 16, 2021 at 12:47:05PM -0500, Simo Sorce wrote:
> Some more info, sorry for the delay.
>
> Currently, as epxlained eralier, the HKDF is approved only in specific
> cases (from SP.800-56C rev 2), which is why I asked Jeff to inquire if
> KDF agility was possible for fscrypt.
>
> That said, we are also trying to get NIST to approve HKDF for use in
> SP800-133 covered scenarios (Symmetric Keys Derived from Pre-Existing
> Key), which is the case applicable to fscrypt (afaict).
>
> SP.800-133 currently only allows KDFs as defined in SP.800-108, but
> there is hope that SP.800-56C rev 2 KDFs can be alloed also, after all
> they are already allowed for key-agreement schemes.
>
> Hope this clears a bit why we inquired, it is just in case, for
> whatever reason, NIST decided not to approve or delays a decision; to
> be clear, there is nothing wrong in HKDF itself that we know of.
>
Just getting HKDF properly approved seems like a much better approach than doing
a lot of work for nothing. Not just for fscrypt but also for everything else
using HKDF.
- Eric
next prev parent reply other threads:[~2021-02-16 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 13:14 fscrypt and FIPS Jeff Layton
2021-02-10 17:49 ` Eric Biggers
2021-02-10 19:28 ` Jeff Layton
2021-02-10 20:07 ` Thibaud Ecarot
2021-02-10 20:12 ` Simo Sorce
2021-02-16 17:47 ` Simo Sorce
2021-02-16 19:04 ` Eric Biggers [this message]
2021-02-16 19:22 ` Simo Sorce
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=YCwXSwseAoMdkXGG@gmail.com \
--to=ebiggers@kernel.org \
--cc=jlayton@redhat.com \
--cc=linux-fscrypt@vger.kernel.org \
--cc=simo@redhat.com \
--cc=thibaud.ecarot@gmail.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;
as well as URLs for NNTP newsgroup(s).