[tahoe-dev] [pycryptopp] #24: SHA256 failure on NetBSD with multiple segments

[pycryptopp]

#24: SHA256 failure on NetBSD with multiple segments
----------------------+-----------------------------------------------------
Reporter:  warner     |           Owner:  bdew 
    Type:  defect     |          Status:  new  
Priority:  critical   |         Version:  0.5.1
Keywords:  integrity  |   Launchpad_bug:       
----------------------+-----------------------------------------------------

Comment(by zooko):

 When a standard Crypto++ source tree is built (i.e., not the special
 embedded build in pycryptopp) then it produces a file named
 {{{cryptest.exe}}} (even on Unix).  If you run {{{./cryptest.exe v}}} then
 it will execute the Crypto++ self-tests.  (If you run {{{./cryptest.exe
 b}}} then it will execute the benchmarks.)

 I don't know yet whether the self-tests exercise the same paths of
 hashing, as Brian described in the original issue report:

 "two updates, in which the total number of bytes is a multiple of 128, and
 in which the first write is an odd number less than 64, will cause this
 bug."

-- 
Ticket URL: <http://allmydata.org/trac/pycryptopp/ticket/24#comment:11>
pycryptopp <http://allmydata.org/trac/pycryptopp>
Python bindings for the Crypto++ library