[tahoe-dev] [pycryptopp] #31: segfault in rsa.so

pycryptopp trac at allmydata.org
Sun Oct 25 19:18:10 UTC 2009


#31: segfault in rsa.so
---------------------+------------------------------------------------------
Reporter:  zooko     |           Owner:        
    Type:  defect    |          Status:  new   
Priority:  critical  |         Version:  0.5.17
Keywords:  security  |   Launchpad_bug:        
---------------------+------------------------------------------------------

Comment(by zooko):

 Hm.  I set up a builder which uses the system-supplied libcrypto++ (on
 Karmic) and it passes:

 http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-
 karmic-yukyuk-syslib

 Although the builder on the same machine that is building the embedded
 copy of libcrypto++ segfaults:

 http://allmydata.org/buildbot-pycryptopp/builders/linux-amd64-ubuntu-
 karmic-yukyuk

 This suggests that there is a bug in the embedded copy, right?  But it
 doesn't appear on any other builders.  So possibly there is a bug
 interaction between the embedded copy of libcrypto++ and the version of
 g++ that is in Karmic Koala?  I just added to the show-tool-versions step
 to emit what version of g++ is present on each platform.

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


More information about the tahoe-dev mailing list