Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Stephan Mueller <smueller@chronox.de>
To:     Anshuman Gupta <anshuman.gupta@intel.com>
Cc:     linux-crypto@vger.kernel.org
Subject: Re: [Query] RSA SHA-384 signature verification
Date:   Mon, 15 Jun 2020 21:25:58 +0200
Message-ID: <1730161.mygNopSbl3@tauon.chronox.de>
In-Reply-To: <20200615170413.GF14085@intel.com>
References: <20200615170413.GF14085@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Am Montag, 15. Juni 2020, 19:04:14 CEST schrieb Anshuman Gupta:

Hi Anshuman,

> Hi ,
> I wanted to verify a RSA SHA-384 signature.
> I am using crypto_alloc_shash(), crypto_shash_digest() API to extract
> the SHA-384 digest.
> I am having public key along with the sha-384 digest extracted from raw data
> and signature. AFAIU understand from crypto documentation that i need to
> verify the signature by importing public key to akcipher/skcipher API.
> Here i am not sure which cipher API to prefer symmetric key cipher or
> asymmetric key cipher API.
> 
> There are two types of API to import the key.
> crypto_skcipher_setkey()
> crypto_akcipher_set_pub_key()
> 
> Also i am not sure exactly which algo to use for RSA-SHA384 signature
> verification.
> 
> Any help or inputs from crypto community will highly appreciated.

akcipher: asymmetric key crypto

skcipher: symmetric key crypto
> 
> Thanks ,
> Anshuman Gupta.


Ciao
Stephan