From: David Woodhouse <dwmw2@infradead.org>
To: Tadeusz Struk <tadeusz.struk@intel.com>,
David Howells <dhowells@redhat.com>,
Tadeusz Struk <tstruk@gmail.com>
Cc: herbert@gondor.apana.org.au, smueller@chronox.de,
linux-api@vger.kernel.org, marcel@holtmann.org,
linux-kernel@vger.kernel.org, keyrings@vger.kernel.org,
linux-crypto@vger.kernel.org, zohar@linux.vnet.ibm.com
Subject: Re: [PATCH v2] crypto: AF_ALG - add support for keys/asymmetric-type
Date: Wed, 13 Jan 2016 15:06:33 +0000 [thread overview]
Message-ID: <1452697593.88154.49.camel@infradead.org> (raw)
In-Reply-To: <569659AC.9070506@intel.com>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
On Wed, 2016-01-13 at 06:05 -0800, Tadeusz Struk wrote:
>
> I agree, ideally keyctl should do the job for all the cases and
> request_key() should just return a key data.
No, you can NOT RELY ON HAVING THE KEY DATA. It might be in hardware.
You might have something which will perform sign/verify/encrypt/decrypt
operations *with* the key at your request, but which can never just
*give* you the key.
Any crypto API which relies on *having* the key is fundamentally wrong.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5691 bytes --]
next prev parent reply other threads:[~2016-01-13 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 15:50 Tadeusz Struk
2016-01-12 5:56 ` Tadeusz Struk
2016-01-13 12:27 ` David Woodhouse
2016-01-13 13:52 ` Tadeusz Struk
2016-01-13 13:31 ` David Howells
2016-01-13 14:05 ` Tadeusz Struk
2016-01-13 15:06 ` David Woodhouse [this message]
2016-01-13 16:14 ` Tadeusz Struk
2016-01-16 10:51 ` David Howells
2016-01-13 13:36 ` David Howells
2016-01-13 13:45 ` David Woodhouse
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=1452697593.88154.49.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=smueller@chronox.de \
--cc=tadeusz.struk@intel.com \
--cc=tstruk@gmail.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
all inboxes | Powered by JetHome®