| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 15 Jun 2015 21:48:22 -0700 From: Tadeusz Struk <tadeusz.struk@...el.com> To: Herbert Xu <herbert@...dor.apana.org.au> CC: linux-kernel@...r.kernel.org, keescook@...omium.org, jwboyer@...hat.com, smueller@...onox.de, richard@....at, steved@...hat.com, qat-linux@...el.com, dhowells@...hat.com, linux-crypto@...r.kernel.org, james.l.morris@...cle.com, jkosina@...e.cz, zohar@...ux.vnet.ibm.com, davem@...emloft.net, vgoyal@...hat.com Subject: Re: [PATCH RFC v5 2/4] crypto: add PKE API On 06/15/2015 09:06 PM, Herbert Xu wrote: >> No, it will handle whatever it will find. So if a public key will be passed it will only set "n" and "e". >> > If a private key will be passed it will set all three "n", "e", and "d". >> > Then during operation I check if there is everything that's required. > AFAICS the ASN1 parser will call all three functions and bomb out > if any one of them fails. If you did make them all optional then > you'd need to check to ensure that at least n and e are present. > > Also all your test vectors contain private keys. Please add at > least one that contains a public key only to test this. I've just tested it and it works fine for both private and public keys. I'll add one vector to test only public key case. Thanks -- 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