diff options
author | Jarod Wilson <jarod@redhat.com> | 2008-11-24 21:20:13 +0800 |
---|---|---|
committer | Herbert Xu <herbert@gondor.apana.org.au> | 2008-12-25 11:01:49 +1100 |
commit | 95b60fa192e030e4105b383ea55ae3eb67686d67 (patch) | |
tree | a4e4c17985d9c703cd4fa5fc4b0a8617cd75baf7 /crypto/fcrypt.c | |
parent | 513fc239dfba1bc8b43b2f36ee4ea4b08ddaa350 (diff) | |
download | linux-crypto-95b60fa192e030e4105b383ea55ae3eb67686d67.tar.gz linux-crypto-95b60fa192e030e4105b383ea55ae3eb67686d67.zip |
crypto: ansi_cprng - fix inverted DT increment routine
The ANSI X9.31 PRNG docs aren't particularly clear on how to increment DT,
but empirical testing shows we're incrementing from the wrong end. A 10,000
iteration Monte Carlo RNG test currently winds up not getting the expected
result.
From http://csrc.nist.gov/groups/STM/cavp/documents/rng/RNGVS.pdf :
# CAVS 4.3
# ANSI931 MCT
[X9.31]
[AES 128-Key]
COUNT = 0
Key = 9f5b51200bf334b5d82be8c37255c848
DT = 6376bbe52902ba3b67c925fa701f11ac
V = 572c8e76872647977e74fbddc49501d1
R = 48e9bd0d06ee18fbe45790d5c3fc9b73
Currently, we get 0dd08496c4f7178bfa70a2161a79459a after 10000 loops.
Inverting the DT increment routine results in us obtaining the expected result
of 48e9bd0d06ee18fbe45790d5c3fc9b73. Verified on both x86_64 and ppc64.
Signed-off-by: Jarod Wilson <jarod@redhat.com>
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions