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
Date: Mon, 15 Jun 2020 22:34:14 +0530 [thread overview]
Message-ID: <20200615170413.GF14085@intel.com> (raw)
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.
next reply other threads:[~2020-06-15 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 17:04 Anshuman Gupta [this message]
2020-06-15 19:25 ` [Query] RSA SHA-384 signature verification Stephan Mueller
2020-06-16 3:56 ` Anshuman Gupta
2020-06-16 5:03 ` Stephan Mueller
2020-06-17 10:09 ` Anshuman Gupta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200615170413.GF14085@intel.com \
--to=anshuman.gupta@intel.com \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).