From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tadeusz Struk Subject: Re: [PATCH RFC v5 2/4] crypto: add PKE API Date: Mon, 15 Jun 2015 20:36:06 -0700 Message-ID: <557F99A6.3010904@intel.com> References: <20150615201831.15697.57738.stgit@tstruk-mobl1> <20150615201842.15697.59701.stgit@tstruk-mobl1> <20150616000519.GA16973@gondor.apana.org.au> <557F83DF.2090003@intel.com> <20150616022751.GA19040@gondor.apana.org.au> <557F8CCA.2080405@intel.com> <20150616032511.GA19977@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, keescook@chromium.org, jwboyer@redhat.com, smueller@chronox.de, richard@nod.at, steved@redhat.com, qat-linux@intel.com, dhowells@redhat.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 To: Herbert Xu Return-path: Received: from mga14.intel.com ([192.55.52.115]:31973 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750763AbbFPDgL (ORCPT ); Mon, 15 Jun 2015 23:36:11 -0400 In-Reply-To: <20150616032511.GA19977@gondor.apana.org.au> Sender: linux-crypto-owner@vger.kernel.org List-ID: On 06/15/2015 08:25 PM, Herbert Xu wrote: > The current parse_key function requires all three number to be > present, n, e, and d, no? 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.