From: "Stephan Müller" <smueller@chronox.de>
To: dhowells@redhat.com
Cc: herbert@gondor.apana.org.au, mathew.j.martineau@linux.intel.com,
linux-crypto@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH v5] KEYS: add SP800-56A KDF support for DH
Date: Fri, 10 Feb 2017 14:18:52 +0100 [thread overview]
Message-ID: <2372333.Xj222SvEfc@tauon.atsec.com> (raw)
In-Reply-To: <1571629.ErTDR5PMQO@positron.chronox.de>
Am Freitag, 19. August 2016, 20:39:09 CET schrieb Stephan Mueller:
Hi David,
> Hi,
>
> This patch now folds the KDF into the keys support as requested by
> Herbert. The caller can only supply the hash name used for the KDF.
>
> Note, the KDF implementation is identical to the kdf_ctr() support in
> the now unneeded KDF patches to the kernel crypto API.
>
> The new patch also changes the variable name from kdfname to hashname.
>
> Also, the patch adds a missing semicolon.
>
> Finally, the patch adds a guard against compiling the compat code
> if the general Linux kernel configuration does not have the compat
> code enabled. Without that guard, compilation warnings are seen.
May I ask which plans do you have with the KDF support for DH?
Ciao
Stephan
next prev parent reply other threads:[~2017-02-10 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 18:39 [PATCH v5] KEYS: add SP800-56A KDF support for DH Stephan Mueller
2016-08-19 18:40 ` [PATCH v5] DH support: add KDF handling support Stephan Mueller
2017-04-03 22:22 ` David Howells
2017-04-03 23:18 ` Stephan Müller
2017-04-03 22:28 ` David Howells
2016-09-20 12:51 ` [PATCH v5] KEYS: add SP800-56A KDF support for DH Stephan Mueller
2017-02-10 13:18 ` Stephan Müller [this message]
2017-04-03 23:04 ` David Howells
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=2372333.Xj222SvEfc@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mathew.j.martineau@linux.intel.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).