Custom Query (72 matches)
Results (40 - 42 of 72)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #45 | fixed | upgrade to latest Crypto++ with SHA-256 bugfixes | zooko | |
| Description |
copy in the latest Crypto++ patches for SHA-256 and any other new patches that we ought to bundle |
|||
| #44 | fixed | test what happens if another Python module loads Crypto++ dynamic link library | zooko | zooko |
| Description |
In theory, it will cause crashes or possibly exploitable holes on some platforms. |
|||
| #43 | fixed | add a quick start-up self test for SHA-256 | zooko | |
| Description |
Add a "quick start-up self test" to pycryptopp which exercises the SHA-256 code at a minimal cost in time. This would be analogous to the "quick start-up self test" that for AES: http://tahoe-lafs.org/trac/pycryptopp/changeset/683/trunk I guess for the SHA-256 test I would just copy this one unit test which exercises different chunk sizes: http://tahoe-lafs.org/trac/pycryptopp/browser/trunk/pycryptopp/test/test_sha256.py?rev=692#L87 I guess that would *not* (probably) exercise the really weird cases such as the input crossing 0x80000000, but it would give me some confidence. Users of pycryptopp would be encouraged to execute the quick startup self test one time after loading pycryptopp. |
|||
