[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1452697593.88154.49.camel@infradead.org>
Date: Wed, 13 Jan 2016 15:06:33 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Tadeusz Struk <tadeusz.struk@...el.com>,
David Howells <dhowells@...hat.com>,
Tadeusz Struk <tstruk@...il.com>
Cc: herbert@...dor.apana.org.au, smueller@...onox.de,
linux-api@...r.kernel.org, marcel@...tmann.org,
linux-kernel@...r.kernel.org, keyrings@...r.kernel.org,
linux-crypto@...r.kernel.org, zohar@...ux.vnet.ibm.com
Subject: Re: [PATCH v2] crypto: AF_ALG - add support for keys/asymmetric-type
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
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (5691 bytes)
Powered by blists - more mailing lists