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

[pycryptopp]

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

Comment(by zooko):

 Oh, there is another thing to test -- what if you link to an external
 {{{libcryptopp.so}}} instead of building the embedded version of Crypto++?
 Maybe our build process introduces a bug into the resulting Crypto++
 object code that isn't present in the upstream build or the Debian or
 NetBSD builds.  I tried both embedded and external on my Linux workstation
 yukyuk with no difference in behavior.  If Black Dew and Midnight Magic
 could try it on their machines where the tests fail that might be
 informative.

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