From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
sfr@canb.auug.org.au, "Jason A. Donenfeld" <Jason@zx2c4.com>
Subject: [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function
Date: Wed, 11 Dec 2019 10:26:39 +0100 [thread overview]
Message-ID: <20191211092640.107621-1-Jason@zx2c4.com> (raw)
In-Reply-To: <20191211102455.7b55218e@canb.auug.org.au>
Somehow this was forgotten when Zinc was being split into oddly shaped
pieces, resulting in linker errors. The x86_64 glue has a specific key
generation implementation, but the Arm one does not. However, it can
still receive the NEON speedups by calling the ordinary DH function
using the base point.
Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
---
arch/arm/crypto/curve25519-glue.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/crypto/curve25519-glue.c b/arch/arm/crypto/curve25519-glue.c
index f3f42cf3b893..776ae07e0469 100644
--- a/arch/arm/crypto/curve25519-glue.c
+++ b/arch/arm/crypto/curve25519-glue.c
@@ -38,6 +38,13 @@ void curve25519_arch(u8 out[CURVE25519_KEY_SIZE],
}
EXPORT_SYMBOL(curve25519_arch);
+void curve25519_base_arch(u8 pub[CURVE25519_KEY_SIZE],
+ const u8 secret[CURVE25519_KEY_SIZE])
+{
+ return curve25519_arch(pub, secret, curve25519_base_point);
+}
+EXPORT_SYMBOL(curve25519_base_arch);
+
static int curve25519_set_secret(struct crypto_kpp *tfm, const void *buf,
unsigned int len)
{
--
2.24.0
next parent reply other threads:[~2019-12-11 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191211102455.7b55218e@canb.auug.org.au>
2019-12-11 9:26 ` Jason A. Donenfeld [this message]
2019-12-11 9:26 ` [PATCH 2/2] crypto: curve25519 - re-add selftests Jason A. Donenfeld
2019-12-11 9:38 ` [PATCH 1/2] crypto: arm/curve25519 - add arch-specific key generation function Ard Biesheuvel
2019-12-11 9:40 ` Jason A. Donenfeld
2019-12-11 12:07 ` Jason A. Donenfeld
2019-12-12 6:08 ` Herbert Xu
2019-12-12 6:08 ` 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=20191211092640.107621-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).