Re: [PATCH v2 00/25] Multiple changes to crypto/ansi_cprng.c

[Stephan Mueller <smueller@chronox.de>]

Am Montag, 15. Dezember 2014, 03:28:16 schrieb George Spelvin:

Hi George,

>> 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.

Good, that is what we need :-)

So, MCT for AES128 is pass then.
>
>> 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.)

Ah, now I see it. Yes, all AES 128 are covered.

What about AES 192 and 256?



Ciao
Stephan