On Mar 12, 2009, at 22:12 PM, Jeffrey Walton wrote:
>> To reproduce this error, install Python,...
> Is there no vanilla test case? For example, if the script is
> failing at a AES test, can you offer up the parameters? I will then
> run the test on an embedded device which has an ARM processor. Does
> the ARM flavor matter? I only have latter versions. I believe they
> are most commonly called 'StrongARMs'.
The code that is most likely at fault is Python-specific code written
by me in my pycryptopp library. Crypto++'s own self-tests
("cryptest.exe v") already exercise the relevant behavior and pass.
The relevant behavior from Crypto++ is to have AES-128 in CTR mode,
and feed in 15 bytes of plaintext, then in a second call to
ProcessData(), process another 17 bytes.
You can see the C++ source code for this function in pycryptopp here:
http://allmydata.org/trac/pycryptopp/browser/pycryptopp/cipher/
aesmodule.cpp?rev=590#L54
The test of this code which stimulates the failure on armel is here
(the test is written in Python):
http://allmydata.org/trac/pycryptopp/browser/pycryptopp/test/
test_aes.py?rev=590#L43
Regards,
Zooko
---
Tahoe, the Least-Authority Filesystem -- http://allmydata.org
store your data: $10/month -- http://allmydata.com/?tracking=zsig
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to [email protected].
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
-~----------~----~----~----~------~----~------~--~---
