From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org, Herbert Xu <herbert@gondor.apana.org.au>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Paul Crowley <paulcrowley@google.com>
Subject: [PATCH v2 0/2] crypto: some hardening against AES cache-timing attacks
Date: Tue, 16 Oct 2018 23:18:11 -0700 [thread overview]
Message-ID: <20181017061813.32751-1-ebiggers@kernel.org> (raw)
This series makes the "aes-fixed-time" and "aes-arm" implementations of
AES more resistant to cache-timing attacks.
Note that even after these changes, the implementations still aren't
necessarily guaranteed to be constant-time; see
https://cr.yp.to/antiforgery/cachetiming-20050414.pdf for a discussion
of the many difficulties involved in writing truly constant-time AES
software. But it's valuable to make such attacks more difficult.
Eric Biggers (2):
crypto: aes_ti - disable interrupts while accessing S-box
crypto: arm/aes - add some hardening against cache-timing attacks
arch/arm/crypto/aes-cipher-core.S | 26 ++++++++++++++++++++++++++
arch/arm/crypto/aes-cipher-glue.c | 13 +++++++++++++
crypto/aes_generic.c | 9 +++++----
crypto/aes_ti.c | 18 ++++++++++++++++++
4 files changed, 62 insertions(+), 4 deletions(-)
--
2.19.1
next reply other threads:[~2018-10-17 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 6:18 Eric Biggers [this message]
2018-10-17 6:18 ` [PATCH v2 1/2] crypto: aes_ti - disable interrupts while accessing S-box Eric Biggers
2018-10-18 4:01 ` Ard Biesheuvel
2018-10-18 4:01 ` Ard Biesheuvel
2018-10-17 6:18 ` [PATCH v2 2/2] crypto: arm/aes - add some hardening against cache-timing attacks Eric Biggers
2018-10-18 3:46 ` Ard Biesheuvel
2018-10-18 3:46 ` Ard Biesheuvel
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=20181017061813.32751-1-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=paulcrowley@google.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