From: David Howells <dhowells@redhat.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dhowells@redhat.com, Tadeusz Struk <tadeusz.struk@intel.com>,
linux-kernel@vger.kernel.org, keescook@chromium.org,
jwboyer@redhat.com, richard@nod.at, steved@redhat.com,
qat-linux@intel.com, linux-crypto@vger.kernel.org,
james.l.morris@oracle.com, jkosina@suse.cz,
zohar@linux.vnet.ibm.com, davem@davemloft.net, vgoyal@redhat.com
Subject: Re: [PATCH RFC v2 1/2] crypto: add PKE API
Date: Mon, 11 May 2015 14:45:27 +0100 [thread overview]
Message-ID: <11243.1431351927@warthog.procyon.org.uk> (raw)
In-Reply-To: <20150511062421.GA2266@gondor.apana.org.au>
Herbert Xu <herbert@gondor.apana.org.au> wrote:
> > + * @capabilities:
> > + * Specifies what operations are provided by the algorithm
> > + * implementation.
>
> Don't do this. It's a nightmare for the user to have to deal with
> multiple implementations with differing capabilities.
>
> Make the implementor provide backups/fallbacks.
What if the fallback doesn't exist? For instance, a H/W contained key is
specifically limited to, say, just sign/verify and the not permitted to be
used for encrypt/decrypt. How do you provide a fallback given you can't get
at the key?
David
next prev parent reply other threads:[~2015-05-11 13:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 19:36 [PATCH RFC v2 0/2] crypto: Introduce Public Key Encryption API Tadeusz Struk
2015-05-06 19:36 ` [PATCH RFC v2 1/2] crypto: add PKE API Tadeusz Struk
2015-05-11 6:03 ` Herbert Xu
2015-05-11 6:24 ` Herbert Xu
2015-05-11 6:27 ` Herbert Xu
2015-05-11 6:32 ` Herbert Xu
2015-05-22 18:37 ` Tadeusz Struk
2015-05-23 5:47 ` Herbert Xu
2015-05-23 14:20 ` Tadeusz Struk
2015-05-28 4:08 ` Herbert Xu
2015-05-28 16:54 ` Tadeusz Struk
2015-06-01 5:48 ` Herbert Xu
2015-06-01 17:52 ` Tadeusz Struk
2015-05-11 13:45 ` David Howells [this message]
2015-05-12 1:21 ` Herbert Xu
2015-05-13 15:03 ` David Howells
2015-05-14 2:59 ` Herbert Xu
2015-06-08 19:34 ` Kees Cook
2015-05-06 19:36 ` [PATCH RFC v2 2/2] crypto: RSA: KEYS: convert rsa and public key to new " Tadeusz Struk
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=11243.1431351927@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=james.l.morris@oracle.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=richard@nod.at \
--cc=steved@redhat.com \
--cc=tadeusz.struk@intel.com \
--cc=vgoyal@redhat.com \
--cc=zohar@linux.vnet.ibm.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
Powered by JetHome