From: Eric Biggers <ebiggers@kernel.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au,
Samuel Neves <sneves@dei.uc.pt>,
Andy Polyakov <appro@openssl.org>
Subject: Re: [PATCH crypto-next v6 2/3] crypto: x86_64/poly1305 - add faster implementations
Date: Tue, 17 Dec 2019 18:31:52 -0800 [thread overview]
Message-ID: <20191218023152.GA3636@sol.localdomain> (raw)
In-Reply-To: <20191217174445.188216-3-Jason@zx2c4.com>
On Tue, Dec 17, 2019 at 06:44:44PM +0100, Jason A. Donenfeld wrote:
>
> While this is CRYPTOGAMS code, the originating code for this happens to
> be derived from OpenSSL's commit 4dfe4310c31c4483705991d9a798ce9be1ed1c68.
This doesn't make sense, since there are changes in this patch that are only in
the CRYPTOGAMS version, not in the OpenSSL 4dfe4310c31c version.
>
> Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
> Co-developed-by: Samuel Neves <sneves@dei.uc.pt>
> Co-developed-by: Andy Polyakov <appro@openssl.org>
Each "Co-developed-by" always needs its own "Signed-off-by".
See Documentation/process/submitting-patches.rst
> diff --git a/arch/x86/crypto/poly1305-x86_64.pl b/arch/x86/crypto/poly1305-x86_64.pl
> new file mode 100644
> index 000000000000..f994855cdbe2
> --- /dev/null
> +++ b/arch/x86/crypto/poly1305-x86_64.pl
> @@ -0,0 +1,4266 @@
> +#!/usr/bin/env perl
> +# SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
> +#
> +# Copyright (C) 2017-2018 Samuel Neves <sneves@dei.uc.pt>. All Rights Reserved.
> +# Copyright (C) 2017-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
> +# Copyright (C) 2006-2017 CRYPTOGAMS by <appro@openssl.org>. All Rights Reserved.
> +#
> +# This code is taken from the OpenSSL project but the author, Andy Polyakov,
> +# has relicensed it under the licenses specified in the SPDX header above.
> +# The original headers, including the original license headers, are
> +# included below for completeness.
And this says it's taken from the OpenSSL project, not CRYPTOGAMS.
Also how is this copyright 2006? The newest date in either the OpenSSL or
CRYPTOGAMS versions is March 2015.
Also, can you elaborate on what changes have been made from version actually
being used in production in OpenSSL, and how those changes were vetted? You
keep claiming that this implementation is extremely well vetted in comparison to
the kernel's existing implementation, so presumably you have something in mind.
- Eric
next prev parent reply other threads:[~2019-12-18 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 17:44 [PATCH crypto-next v6 0/3] crypto: poly1305 improvements Jason A. Donenfeld
2019-12-17 17:44 ` [PATCH crypto-next v6 1/3] crypto: poly1305 - add new 32 and 64-bit generic versions Jason A. Donenfeld
2019-12-18 3:03 ` Eric Biggers
2019-12-17 17:44 ` [PATCH crypto-next v6 2/3] crypto: x86_64/poly1305 - add faster implementations Jason A. Donenfeld
2019-12-18 2:31 ` Eric Biggers [this message]
2019-12-17 17:44 ` [PATCH crypto-next v6 3/3] crypto: arm/arm64/mips/poly1305 - remove redundant non-reduction from emit Jason A. Donenfeld
2019-12-18 2:48 ` [PATCH crypto-next v6 0/3] crypto: poly1305 improvements Eric Biggers
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=20191218023152.GA3636@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=Jason@zx2c4.com \
--cc=appro@openssl.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=sneves@dei.uc.pt \
/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