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;
IronPort-SDR: stWnO0CeM5z61j9X8GOLhtCtFD91mYqB+cMk+gY2rcYhL8HHrMc9QxGoiKco/X2rdanTf2Pvyu
 +2xidEoqxDEg==
IronPort-SDR: fNW3/ouO37kjjqkWXJCp8LdVCrVW2sPfqqy1rCKVv9UQ1jSw6YxSeXCor/1RN9U75g010v1MpG
 FZZZqwi02gPQ==
Date:   Mon, 15 Jun 2020 22:34:14 +0530
From:   Anshuman Gupta <anshuman.gupta@intel.com>
To:     linux-crypto@vger.kernel.org
Cc:     anshuman.gupta@intel.com
Subject: [Query] RSA SHA-384 signature verification
Message-ID: <20200615170413.GF14085@intel.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: Mutt/1.9.4 (2018-02-28)
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

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.

Thanks ,
Anshuman Gupta.