From: Stephan Mueller <smueller@chronox.de>
To: Mat Martineau <mathew.j.martineau@linux.intel.com>,
herbert@gondor.apana.org.au
Cc: David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: key retention service: DH support
Date: Tue, 24 May 2016 18:45:09 +0200 [thread overview]
Message-ID: <1542958.TuajgKVjUG@positron.chronox.de> (raw)
In-Reply-To: <alpine.OSX.2.20.1605240851210.7071@tmhoole-mobl2.amr.corp.intel.com>
Am Dienstag, 24. Mai 2016, 09:22:22 schrieb Mat Martineau:
Hi Mat, Herbert
>
> KDF transformations would be extremely useful, but transforming the DH
> output using a KDF needs to be configurable. There are enough different
> uses for DH that it's important to have access to the raw values.
>
> Since the KDF patches are not yet merged, I'm not sure of the best way to
> accomodate the future feature. We could future-proof KEYCTL_DH_COMPUTE by
> adding a 5th arg, an optional pointer to KDF configuration (NAME and
> LABEL). Or a separate KEYCTL_DH_COMPUTE_KDF command can be added later.
With that statement, Herbert, should we start looking into my KDF patches
after the merge window closes?
Ciao
Stephan
next prev parent reply other threads:[~2016-05-24 16:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 18:57 key retention service: DH support Stephan Mueller
2016-05-24 7:04 ` David Howells
2016-05-24 7:14 ` Stephan Mueller
2016-05-24 7:19 ` David Howells
2016-05-24 7:29 ` Stephan Mueller
2016-05-24 16:22 ` Mat Martineau
2016-05-24 16:45 ` Stephan Mueller [this message]
2016-05-25 10:25 ` Herbert Xu
2016-05-25 10:58 ` David Howells
2016-05-26 17:04 ` Mat Martineau
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=1542958.TuajgKVjUG@positron.chronox.de \
--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