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 v3 0/2] crypto: some hardening against AES cache-timing attacks
Date: Wed, 17 Oct 2018 21:37:57 -0700 [thread overview]
Message-ID: <20181018043759.7669-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.
Changed since v2:
- In aes-arm, move the IRQ disable/enable into the assembly file.
- Other aes-arm tweaks.
- Add Kconfig help text.
Thanks to Ard Biesheuvel for the suggestions.
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/Kconfig | 9 +++++
arch/arm/crypto/aes-cipher-core.S | 62 ++++++++++++++++++++++++++-----
crypto/Kconfig | 3 +-
crypto/aes_generic.c | 9 +++--
crypto/aes_ti.c | 18 +++++++++
5 files changed, 86 insertions(+), 15 deletions(-)
--
2.19.1
next reply other threads:[~2018-10-18 12:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 4:37 Eric Biggers [this message]
2018-10-18 4:37 ` [PATCH v3 1/2] crypto: aes_ti - disable interrupts while accessing S-box Eric Biggers
2018-10-18 4:37 ` [PATCH v3 2/2] crypto: arm/aes - add some hardening against cache-timing attacks Eric Biggers
2018-10-19 5:41 ` Ard Biesheuvel
2018-10-19 9:54 ` Ard Biesheuvel
2018-10-19 20:39 ` Eric Biggers
2018-10-20 2:34 ` Ard Biesheuvel
2018-10-19 20:30 ` Eric Biggers
2018-11-09 9:49 ` [PATCH v3 0/2] crypto: some hardening against AES " Herbert Xu
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=20181018043759.7669-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.