On Tue, Dec 02, 2014 at 03:03:38PM -0500, George Spelvin wrote: > > I'm only ok with removing I if you can continue to be able to output it. > > given that I is listed as part of the test sequences that NIST provides, > > I'd like to be able to compare the values. > > I can do that easily, but I can't print the *input* I, which > is the result of encrypting the previous DT, as it's thrown > away earlier. > > You'd have to look further back in the debug messages to find it. > > Is changing the format of the debug messages okay? I'd like the debug > messages to describe the code, but I don't know if you have something > that parses the current output. > I'm fine with changing the output, as I don't think anything particularly relies on the format, but I cant' speak for others Neil > > The test output I see on p. 33 of > http://csrc.nist.gov/groups/STM/cavp/documents/rng/RNGVS.pdf > doesn't include I. Can you point me to a sample that includes I? > > It might be best to more significantly rework the debug messages to > resemble the NIST test vectors. > -- > 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 > -- 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