From: Stephan Mueller <smueller@chronox.de>
To: Tudor Ambarus <tudor-dan.ambarus@nxp.com>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
horia.geanta@nxp.com
Subject: Re: [PATCH v6 0/3] crypto: caam - add support for RSA algorithm
Date: Thu, 19 May 2016 23:51 +0200 [thread overview]
Message-ID: <2370625.CgO9A4qjJ6@positron.chronox.de> (raw)
In-Reply-To: <1463660118-19188-1-git-send-email-tudor-dan.ambarus@nxp.com>
Am Donnerstag, 19. Mai 2016, 15:15:15 schrieb Tudor Ambarus:
Hi Tudor,
as I am looking into the RSA countermeasures, I am wondering how much of
countermeasures are actually applied inside hardware implementations. Can you
please point me to or illustrate any countermeasures your implementation does?
The goal for my question is to identify whether we need to have a generic
implementation one that is enabled on a per-implementation basis.
Ciao
Stephan
next prev parent reply other threads:[~2016-05-19 21:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 12:15 [PATCH v6 0/3] crypto: caam - add support for RSA algorithm Tudor Ambarus
2016-05-19 12:15 ` [PATCH v6 1/3] crypto: scatterwak - Add scatterwalk_sg_copychunks Tudor Ambarus
2016-05-19 12:15 ` [PATCH v6 2/3] crypto: scatterwalk - export scatterwalk_pagedone Tudor Ambarus
2016-05-19 12:15 ` [PATCH v6 3/3] crypto: caam - add support for RSA algorithm Tudor Ambarus
2016-05-19 15:13 ` Horia Ioan Geanta Neag
2016-05-19 15:45 ` [PATCH v6 0/3] " Horia Ioan Geanta Neag
2016-05-19 21:51 ` Stephan Mueller [this message]
2016-05-23 12:56 ` Tudor-Dan Ambarus
2016-05-23 13:02 ` Stephan Mueller
2016-05-24 16:13 ` Tudor-Dan Ambarus
2016-05-24 16:58 ` Stephan Mueller
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=2370625.CgO9A4qjJ6@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=tudor-dan.ambarus@nxp.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