* [PATCH] crypto: adiantum - propagate CRYPTO_ALG_ASYNC flag to instance
@ 2018-12-05 0:46 Eric Biggers
2018-12-13 10:32 ` Herbert Xu
0 siblings, 1 reply; 2+ messages in thread
From: Eric Biggers @ 2018-12-05 0:46 UTC (permalink / raw)
To: linux-crypto, Herbert Xu
From: Eric Biggers <ebiggers@google.com>
If the stream cipher implementation is asynchronous, then the Adiantum
instance must be flagged as asynchronous as well. Otherwise someone
asking for a synchronous algorithm can get an asynchronous algorithm.
There are no asynchronous xchacha12 or xchacha20 implementations yet
which makes this largely a theoretical issue, but it should be fixed.
Fixes: 059c2a4d8e16 ("crypto: adiantum - add Adiantum support")
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
crypto/adiantum.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/crypto/adiantum.c b/crypto/adiantum.c
index 2dfcf12fd4529..ca27e0dc2958c 100644
--- a/crypto/adiantum.c
+++ b/crypto/adiantum.c
@@ -590,6 +590,8 @@ static int adiantum_create(struct crypto_template *tmpl, struct rtattr **tb)
hash_alg->base.cra_driver_name) >= CRYPTO_MAX_ALG_NAME)
goto out_drop_hash;
+ inst->alg.base.cra_flags = streamcipher_alg->base.cra_flags &
+ CRYPTO_ALG_ASYNC;
inst->alg.base.cra_blocksize = BLOCKCIPHER_BLOCK_SIZE;
inst->alg.base.cra_ctxsize = sizeof(struct adiantum_tfm_ctx);
inst->alg.base.cra_alignmask = streamcipher_alg->base.cra_alignmask |
--
2.20.0.rc1.387.gf8505762e3-goog
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] crypto: adiantum - propagate CRYPTO_ALG_ASYNC flag to instance
2018-12-05 0:46 [PATCH] crypto: adiantum - propagate CRYPTO_ALG_ASYNC flag to instance Eric Biggers
@ 2018-12-13 10:32 ` Herbert Xu
0 siblings, 0 replies; 2+ messages in thread
From: Herbert Xu @ 2018-12-13 10:32 UTC (permalink / raw)
To: Eric Biggers; +Cc: linux-crypto
On Tue, Dec 04, 2018 at 04:46:54PM -0800, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> If the stream cipher implementation is asynchronous, then the Adiantum
> instance must be flagged as asynchronous as well. Otherwise someone
> asking for a synchronous algorithm can get an asynchronous algorithm.
>
> There are no asynchronous xchacha12 or xchacha20 implementations yet
> which makes this largely a theoretical issue, but it should be fixed.
>
> Fixes: 059c2a4d8e16 ("crypto: adiantum - add Adiantum support")
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> crypto/adiantum.c | 2 ++
> 1 file changed, 2 insertions(+)
Patch 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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2018-12-13 10:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-12-05 0:46 [PATCH] crypto: adiantum - propagate CRYPTO_ALG_ASYNC flag to instance Eric Biggers
2018-12-13 10:32 ` Herbert Xu
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.