From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, smueller@chronox.de
Cc: herbert@gondor.apana.org.au, linux-crypto@vger.kernel.org,
nhorman@tuxdriver.com
Subject: Re: [PATCH v2 00/25] Multiple changes to crypto/ansi_cprng.c
Date: 15 Dec 2014 03:28:16 -0500 [thread overview]
Message-ID: <20141215082816.9004.qmail@ns.horizon.com> (raw)
In-Reply-To: <9786224.Pe6urDKot3@tachyon.chronox.de>
> That output is good for the VST test vectors. For the MCT vectors, I need the
> 10000th value.
That was test 9 in the first group:
> [167586.784923] COUNT = 9
> [167586.784925] Key = 10379b53317a2500879e88ad445ea387
> [167586.784927] DT = 055a913d7587d54ee58c053fd4beb4a2
> [167586.784928] V = a7d058a34e1bf49b40f0b6d26661f889
> [167586.791891] R = c252c3f173558775929fe3fb8345feb2
> [167586.791892] cprng: Test 9 passed
> [167586.797633] cprng: Stutter test 9 passed
Just like the CAVS test vectors, I don't print the "loops" value
anywhere.
> With some minor editor massaging (deleting the timestamps and
> inserting a blank line before every "COUNT" line), it matches the
> ANSI931_AES128MCT.fax and ANSI931_AES128VST.fax you sent. I left it
> un-massaged as some sort of evidence that it isn't just a direct copy.
> I cannot match these test vectors and the results to the ones I sent to you.
> E.g. I do not find the key value f3b1666d13607242ed061cabb8d46202 anywhere in
> the data set.
Sorry, that's the union of the testmgr.h tests, a couple I added by hand,
and (at the end) the ones you sent me.
So no, you can't find all of my test results in your test vectors, but
all of your test vectors are in my test results.
(In all cases, the software compares the results with the expected answers.)
next prev parent reply other threads:[~2014-12-15 8:28 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 12:26 [PATCH v2 00/25] Multiple changes to crypto/ansi_cprng.c George Spelvin
2014-12-07 12:26 ` [PATCH v2 01/25] crypto: ansi_cprng - unroll _get_more_prng_bytes George Spelvin
2014-12-07 12:26 ` [PATCH v2 02/25] crypto: ansi_cprng - Additional _get_more_prng_bytes cleanup George Spelvin
2014-12-07 12:26 ` [PATCH v2 03/25] crypto: ansi_cprng - Use %phN rather than print_hex_dump for debug George Spelvin
2014-12-07 12:26 ` [PATCH v2 04/25] crypto: ansi_cprng - Make debug output more like NIST test vectors George Spelvin
2014-12-07 12:26 ` [PATCH v2 05/25] crypto: ansi_cprng - Eliminate ctx->I and ctx->last_rand_data George Spelvin
2014-12-14 11:50 ` Stephan Mueller
2014-12-14 19:22 ` George Spelvin
2014-12-07 12:26 ` [PATCH v2 06/25] crypto: ansi_cprng - Make cont_test a bool George Spelvin
2014-12-07 12:26 ` [PATCH v2 07/25] crypto: ansi_cprng - Shrink context some more George Spelvin
2014-12-07 12:26 ` [PATCH v2 08/25] crypto: ansi_cprng - Don't call reset_prng_context from cprng_init George Spelvin
2014-12-07 12:26 ` [PATCH v2 09/25] crypto: ansi_cprng - Make length types consistent George Spelvin
2014-12-07 12:26 ` [PATCH v2 10/25] crypto: ansi_cprng - Use u8 data types consistently internally George Spelvin
2014-12-07 12:26 ` [PATCH v2 11/25] crypto: ansi_cprng - Eliminate unused PRNG_FIXED_SIZE flag George Spelvin
2014-12-07 12:26 ` [PATCH v2 12/25] crypto: ansi_cprng - Get rid of rdata buffer in fips_cprng_reset George Spelvin
2014-12-07 12:26 ` [PATCH v2 13/25] crypto: Add appropriate consts to RNG API George Spelvin
2014-12-14 11:39 ` Stephan Mueller
2014-12-07 12:26 ` [PATCH v2 14/25] crypto: tcrypt - Add const qualifiers all over the test code George Spelvin
2014-12-07 12:26 ` [PATCH v2 15/25] crypto: testmgr - Merge seed arrays in struct cprng_testvec George Spelvin
2014-12-07 12:26 ` [PATCH v2 16/25] crypto: testmgr - Report failure on zero-length crypto_rng_get_bytes George Spelvin
2014-12-07 12:26 ` [PATCH v2 17/25] crypto: testmgr - Don't crash if CPRNG test result is large George Spelvin
2014-12-07 12:26 ` [PATCH v2 18/25] crypto: testmgr - Add CPRNG stutter test George Spelvin
2014-12-07 12:26 ` [PATCH v2 19/25] crypto: ansi_cprng - simplify get_prng_bytes George Spelvin
2014-12-07 12:26 ` [PATCH v2 20/25] crypto: ansi_cprng - simplify xor_vectors() to xor_block() George Spelvin
2014-12-07 12:26 ` [PATCH v2 21/25] crypto: ansi_cprng - Rename rand_data_valid more sensibly George Spelvin
2014-12-07 12:26 ` [PATCH v2 22/25] crypto: ansi_cprng - Tweak comments George Spelvin
2014-12-07 12:26 ` [PATCH v2 23/25] crypto: ansi_cprng - Introduce a "union cipherblock" George Spelvin
2014-12-07 12:26 ` [PATCH v2 24/25] crypto: ansi_cprng - Introduce non-deterministic mode George Spelvin
2014-12-07 12:26 ` [PATCH v2 25/25] crypto: ansi_cprng - If non-deterministic, don't buffer old output George Spelvin
2014-12-07 22:49 ` George Spelvin
2014-12-08 14:22 ` Neil Horman
2014-12-08 16:43 ` George Spelvin
2014-12-08 18:07 ` Neil Horman
2014-12-08 20:34 ` George Spelvin
2014-12-14 12:06 ` [PATCH v2 00/25] Multiple changes to crypto/ansi_cprng.c Stephan Mueller
2014-12-14 19:47 ` George Spelvin
2014-12-15 6:18 ` Stephan Mueller
2014-12-14 20:37 ` George Spelvin
2014-12-15 6:14 ` Stephan Mueller
2014-12-15 8:42 ` George Spelvin
2014-12-15 8:50 ` Stephan Mueller
2014-12-15 10:45 ` George Spelvin
2014-12-15 11:08 ` Stephan Mueller
2014-12-15 5:53 ` George Spelvin
2014-12-15 6:27 ` Stephan Mueller
2014-12-15 8:28 ` George Spelvin [this message]
2014-12-15 8:56 ` Stephan Mueller
2014-12-15 10:21 ` George Spelvin
2014-12-15 10:46 ` Stephan Mueller
2014-12-15 11:32 ` Neil Horman
2014-12-15 22:01 ` George Spelvin
2014-12-16 7:22 ` Stephan Mueller
2014-12-16 11:32 ` Neil Horman
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=20141215082816.9004.qmail@ns.horizon.com \
--to=linux@horizon.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--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