Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Stephan Mueller <smueller@chronox.de>
Cc: linux-crypto@vger.kernel.org
Subject: Re: Recent AEAD change: testmgr.c change needed?
Date: Wed, 19 Aug 2015 20:45:50 +0800	[thread overview]
Message-ID: <20150819124550.GA18321@gondor.apana.org.au> (raw)
In-Reply-To: <1732898.70JpgbIL8N@myon.chronox.de>

Hi Staphan:

On Wed, Aug 19, 2015 at 11:48:05AM +0200, Stephan Mueller wrote:
> 
> The recent AEAD change seems to trigger a need to change something in 
> testmgr.c. I ran my test tool trying to invoke all possible permutations of 
> cra_name and cra_driver_name ciphers and got the following:
> 
> [11152.816179] alg: No test for gcm_base(ctr(aes-asm),ghash-generic) 
> (gcm_base(ctr(aes-asm),ghash-generic))

This is a bug in gcm_base.  It should not use the driver name as
its cra_name.  I'll try to fix this.

> [11154.278466] alg: No test for ccm_base(ctr(aes-asm),aes-asm) 
> (ccm_base(ctr(aes-asm),aes-asm))
> [11174.819535] alg: No test for gcm(aes-asm) (gcm_base(ctr(aes-asm),ghash-
> clmulni))
> [11174.819610] alg: No test for rfc4106(gcm(aes-asm)) 
> (rfc4106(gcm_base(ctr(aes-asm),ghash-clmulni)))

Ditto.  gcm should also canonicalise aes-asm in its cra_name.

> [11174.819654] alg: No test for seqiv(rfc4106(gcm(aes-asm))) 
> (seqiv(rfc4106(gcm_base(ctr(aes-asm),ghash-clmulni))))

This is different.  We should definitely add tests for the IV
generators.  Obviously we can't test the randomness but we can
certainly test for correctness.  What we can do is reuse the
test vectors for the underlying algorithms.

Cheers,
-- 
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

  reply	other threads:[~2015-08-19 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  9:48 Recent AEAD change: testmgr.c change needed? Stephan Mueller
2015-08-19 12:45 ` Herbert Xu [this message]
2015-08-20  7:34   ` Herbert Xu

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=20150819124550.GA18321@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=smueller@chronox.de \
    /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