From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
Nitin Kumbhar <nkumbhar@nvidia.com>
Cc: <davem@davemloft.net>, <linux-crypto@vger.kernel.org>
Subject: Re: Re: [PATCH 0/6] Add support for ECDSA algorithm
Date: Tue, 22 Aug 2017 19:14:59 +0300 [thread overview]
Message-ID: <87fcb3cf-b8ae-47de-550e-c76ae47af431@microchip.com> (raw)
In-Reply-To: <20170202135721.GA5289@gondor.apana.org.au>
Hi, Herbert,
On 02/02/2017 03:57 PM, Herbert Xu wrote:
> Yes but RSA had an in-kernel user in the form of module signature
> verification. We don't add algorithms to the kernel without
> actual users. So this patch-set needs to come with an actual
> in-kernel user of ECDSA.
ECDSA can be used by the kernel module signing facility too. Is there
any interest in using ECDSA by the kernel module signing facility?
Thanks,
ta
next prev parent reply other threads:[~2017-08-22 16:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 11:35 [PATCH 0/6] Add support for ECDSA algorithm Nitin Kumbhar
2017-01-20 11:35 ` [PATCH 1/6] crypto: ecc: separate out ecc and ecdh Nitin Kumbhar
2017-01-20 11:35 ` [PATCH 2/6] crypto: ecc: add vli and ecc ops Nitin Kumbhar
2017-01-20 11:35 ` [PATCH 3/6] crypto: ecc: export " Nitin Kumbhar
2017-01-20 11:35 ` [PATCH 4/6] crypto: ecdsa: add ECDSA SW implementation Nitin Kumbhar
2017-01-20 13:06 ` Stephan Müller
2017-01-26 5:52 ` Nitin Kumbhar
2017-01-20 11:36 ` [PATCH 5/6] crypto: testmgr: add ECDSA tests Nitin Kumbhar
2017-01-20 13:19 ` Stephan Müller
2017-01-26 5:58 ` Nitin Kumbhar
2017-01-20 11:36 ` [PATCH 6/6] crypto: tcrypt: add ECDSA test modes Nitin Kumbhar
2017-01-23 14:24 ` [PATCH 0/6] Add support for ECDSA algorithm Herbert Xu
2017-01-26 6:00 ` Nitin Kumbhar
2017-01-26 7:44 ` Stephan Müller
2017-02-02 13:57 ` Herbert Xu
2017-02-03 11:16 ` Nitin Kumbhar
2017-02-06 14:47 ` Stephan Müller
2017-08-22 16:14 ` Tudor Ambarus [this message]
2017-08-22 17:22 ` Sandy Harris
2017-08-23 13:40 ` Tudor Ambarus
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=87fcb3cf-b8ae-47de-550e-c76ae47af431@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=nkumbhar@nvidia.com \
/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).