Messages in this thread | | | Date | Mon, 4 May 2009 19:10:10 +0800 | From | Herbert Xu <> | Subject | Re: [PATCH] crypto: don't raise alarm for no ctr(aes*) tests in fips mode |
| |
On Tue, Apr 28, 2009 at 09:18:22PM -0400, Jarod Wilson wrote: > Per the NIST AESAVS document, Appendix A[1], it isn't possible to > have automated self-tests for counter-mode AES, but people are > misled to believe something is wrong by the message that says there > is no test for ctr(aes). Simply suppress all 'no test for ctr(aes*' > messages if fips_enabled is set to avoid confusion.
This is not true at all. In our implementation the counter is set through the IV so it definitely is possible to test counter mode algorithms in Linux.
Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
| |