Closed Bug 589461 Opened 14 years ago Closed 14 years ago

JM: Stanford Crypto Tests Fail

Categories

(Core :: JavaScript Engine, defect)

x86
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- beta7+

People

(Reporter: sayrer, Assigned: dvander)

References

()

Details

http://bitwiseshiftleft.github.com/sjcl/browserTest/ Stanford JS Crypto has a bunch of tests for AES, HMAC, etc. JM currently fails all of it. Probably something wrong in the harness.
If you download sjcl.js then this is a "reduced" shell test case: load('sjcl.js'); function doStuff() { vector = { key: [0x00000000,0x00000000,0x00000000,0x00000000], pt: [0xf34481ec,0x3cc627ba,0xcd5dc3fb,0x08f273e6], ct: [0x0336763e,0x966d9259,0x5a567cc9,0xce537f5e] }; var aes = new sjcl.cipher.aes(vector.key); print(aes.encrypt(vector.pt)); } doStuff(); Should print: 53900862,-1771204007,1515617481,-833388706 JM prints: 1342725520,359298179,-1938642396,329282821
hg bisect says: changeset: 48633:51ed7672df50 user: David Anderson <danderson@mozilla.com> date: Thu Jul 22 17:34:26 2010 -0700 summary: [JAEGER] Simplify double arithmetic paths.
Assignee: general → dvander
Status: NEW → ASSIGNED
With the patch in bug 589714 we pass "AES official known-answer", "CCM mode", and "OCB 2.0" before failing the rest.
blocking2.0: --- → beta6+
Sjcl works correctly now, so marking this fixed.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
OS: Mac OS X → Windows 7
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.