From: Herbert Xu <herbert@gondor.apana.org.au>
To: Iuliana Prodan <iuliana.prodan@nxp.com>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v3 0/2] crypto: validate inputs for gcm and aes
Date: Fri, 9 Aug 2019 16:18:50 +1000 [thread overview]
Message-ID: <20190809061850.GK10392@gondor.apana.org.au> (raw)
In-Reply-To: <1564578355-9639-1-git-send-email-iuliana.prodan@nxp.com>
On Wed, Jul 31, 2019 at 04:05:53PM +0300, Iuliana Prodan wrote:
> Added inline helper functions to check authsize and assoclen for
> gcm, rfc4106 and rfc4543.
> Added, also, inline helper function to check key length for AES algorithms.
> These are used in the generic implementation of gcm/rfc4106/rfc4543
> and aes.
>
> Changes since v2:
> - rename aes helper functions without crypto_ prefix;
> - change include for gcm.h.
>
> Iuliana Prodan (2):
> crypto: gcm - helper functions for assoclen/authsize check
> crypto: aes - helper function to validate key length for AES
> algorithms
>
> crypto/gcm.c | 41 ++++++++++++++-------------------------
> include/crypto/aes.h | 17 ++++++++++++++++
> include/crypto/gcm.h | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> lib/crypto/aes.c | 8 ++++----
> 4 files changed, 91 insertions(+), 30 deletions(-)
All applied. Thanks.
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2019-08-09 6:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 13:05 [PATCH v3 0/2] crypto: validate inputs for gcm and aes Iuliana Prodan
2019-07-31 13:05 ` [PATCH v3 1/2] crypto: gcm - helper functions for assoclen/authsize check Iuliana Prodan
2019-07-31 13:05 ` [PATCH v3 2/2] crypto: aes - helper function to validate key length for AES algorithms Iuliana Prodan
2019-07-31 13:35 ` [PATCH v3 0/2] crypto: validate inputs for gcm and aes Horia Geanta
2019-08-01 7:14 ` Ard Biesheuvel
2019-08-09 6:18 ` Herbert Xu [this message]
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=20190809061850.GK10392@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=iuliana.prodan@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
/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).