diff options
| author | Eric Biggers <ebiggers@google.com> | 2019-03-31 13:04:16 -0700 |
|---|---|---|
| committer | Herbert Xu <herbert@gondor.apana.org.au> | 2019-04-08 14:42:55 +0800 |
| commit | 2b169ef4349a80ec06e49434ab6b9aa92968b62e (patch) | |
| tree | 4d950238894e297807c8fd57f55db7ab8e0c8c1e /crypto/acompress.c | |
| parent | 4b0d8f61d91baae890e2425f3c9c063fd00d026f (diff) | |
| download | linux-crypto-2b169ef4349a80ec06e49434ab6b9aa92968b62e.tar.gz linux-crypto-2b169ef4349a80ec06e49434ab6b9aa92968b62e.zip | |
crypto: chacha20poly1305 - set cra_name correctly
If the rfc7539 template is instantiated with specific implementations,
e.g. "rfc7539(chacha20-generic,poly1305-generic)" rather than
"rfc7539(chacha20,poly1305)", then the implementation names end up
included in the instance's cra_name. This is incorrect because it then
prevents all users from allocating "rfc7539(chacha20,poly1305)", if the
highest priority implementations of chacha20 and poly1305 were selected.
Also, the self-tests aren't run on an instance allocated in this way.
Fix it by setting the instance's cra_name from the underlying
algorithms' actual cra_names, rather than from the requested names.
This matches what other templates do.
Fixes: 584f430dc4b1 ("crypto: chacha20poly1305 - Add a ChaCha20-Poly1305 AEAD construction, RFC7539")
Cc: <stable@vger.kernel.org> # v4.2+
Cc: Martin Willi <martin@strongswan.org>
Signed-off-by: Eric Biggers <ebiggers@google.com>
Reviewed-by: Martin Willi <martin@strongswan.org>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to 'crypto/acompress.c')
0 files changed, 0 insertions, 0 deletions