On Tuesday 05 May 2009 01:29:05 Herbert Xu wrote: > On Mon, May 04, 2009 at 11:45:08PM -0400, Jarod Wilson wrote: > > > > Can't keep all the RFCs and SPs and whatnot straight in my head, and they > > aren't in front of me, but I thought I read that the basic counter increment > > routine wasn't mandated to be any specific way, the only mandate was to > > ensure unique values. Suggestions for how to do so were made though. > > It doesn't matter what is or isn't specified for CTR, the thing > that we call "ctr" is the one that's used for RFC 3686, CCM, and > GCM. It is completely pinned down and can be tested. There are two different "can be tested" contexts here. I completely agree that ctr(aes) is testable within the tcrypt/testmgr context, and sent a patch for such in this thread yesterday. The other context is FIPS CAVS testing, which NIST is saying can't be done, and I was attempting to understand why, which probably only served to muddy the waters. We can definitely do self-tests for ctr(aes). -- Jarod Wilson jarod@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
