From: "Stephan Müller" <smueller@chronox.de>
To: "Stephan Müller" <smueller@chronox.de>
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 0/2] fix authenc() kernel crash
Date: Sun, 24 Sep 2017 08:28:31 +0200 [thread overview]
Message-ID: <5715632.7er1IYYKWG@positron.chronox.de> (raw)
In-Reply-To: <3874163.dZU00zCVt8@positron.chronox.de>
Am Sonntag, 24. September 2017, 08:22:54 CEST schrieb Stephan Müller:
Hi Herbert,
(private)
> Hi Herbert,
>
> The two patches together fix a kernel crash that can be triggered via
> AF_ALG when using authenc() with zero plaintext.
>
> The changes are also tested to verify that the hashing on null data
> is still supported.
You can test / verify the patch with the HEAD code of libkcapi found in [1].
Please execute:
./configure --enable-kcapi-test
make
bin/kcapi -h -x 2 -c "authenc(hmac(sha256),cbc(aes))" -d 2
Note, the last command may take a couple of seconds.
[1] https://github.com/smuellerDD/libkcapi
Ciao
Stephan
prev parent reply other threads:[~2017-09-24 6:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 6:22 [PATCH 0/2] fix authenc() kernel crash Stephan Müller
2017-09-24 6:24 ` [PATCH 1/2] crypto: skcipher - noop for enc/dec with NULL data Stephan Müller
2017-10-07 2:46 ` Herbert Xu
2017-10-07 2:49 ` Stephan Müller
2017-10-07 2:51 ` Herbert Xu
2017-10-07 2:53 ` Stephan Müller
2017-10-07 3:07 ` Herbert Xu
2017-10-07 3:21 ` Stephan Müller
2017-10-07 3:29 ` Herbert Xu
2017-10-07 12:56 ` Stephan Müller
2017-10-09 14:19 ` Herbert Xu
2017-10-09 15:13 ` Stephan Müller
2017-10-09 15:30 ` [PATCH v2] crypto: shash - Fix zero-length shash ahash digest crash Herbert Xu
2017-10-09 15:52 ` Stephan Müller
2017-09-24 6:25 ` [PATCH 2/2] crypto: shash - no kmap of zero SG Stephan Müller
2017-10-07 2:44 ` Herbert Xu
2017-09-24 6:28 ` Stephan Müller [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=5715632.7er1IYYKWG@positron.chronox.de \
--to=smueller@chronox.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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 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.