[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5543D3BE.3000904@intel.com>
Date: Fri, 01 May 2015 12:27:58 -0700
From: Tadeusz Struk <tadeusz.struk@...el.com>
To: David Howells <dhowells@...hat.com>
CC: herbert@...dor.apana.org.au, corbet@....net, keescook@...omium.org,
qat-linux@...el.com, jwboyer@...hat.com, richard@....at,
d.kasatkin@...sung.com, linux-kernel@...r.kernel.org,
steved@...hat.com, vgoyal@...hat.com, james.l.morris@...cle.com,
jkosina@...e.cz, zohar@...ux.vnet.ibm.com, davem@...emloft.net,
jdelvare@...e.de, linux-crypto@...r.kernel.org
Subject: Re: [PATCH RFC 2/2] crypto: RSA: KEYS: convert rsa and public key
to new PKE API
On 05/01/2015 09:21 AM, David Howells wrote:
>> + .verify = RSA_verify_signature,
>> > + .capabilities = PKEY_CAN_VERIFY,
> Can we keep .verify_signature as the name of the first. The second is
> redundant given the function pointers.
I'm thinking that .verify will be more generic. If in the future
we would like to implement something that verifies not a signature, but
for instance is a number is a prime, then we can register a "prime" alg
that implements verify and returns true if a number is a prime.
>
> Given that X.509 certs can hang around for a very long time, having a tfm in
> the cert is probably a bad idea as it may pin resources such as crypto h/w.
>
>> > - ctx->cert->pub->pkey_algo = PKEY_ALGO_RSA;
>> > -
> I think you need this rather than the above. You should only get the tfm when
> you actually need it.
>
That's a good point.
Thank you David for all your comments. I'll rework my patches and send v2 soon.
I'll also try to integrate it with your sign-file as you suggested.
Thanks
T
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists