[tahoe-lafs-trac-stream] [pycryptopp] #76: segfault when using embedded Crypto++ on x86_64, assembly disabled, and no AESNI
pycryptopp
trac at tahoe-lafs.org
Fri Dec 23 06:59:39 UTC 2011
#76: segfault when using embedded Crypto++ on x86_64, assembly disabled, and no
AESNI
-------------------+-------------------------
Reporter: zooko | Owner:
Type: defect | Status: closed
Priority: major | Milestone:
Version: 0.5.29 | Resolution: invalid
Keywords: | Launchpad Bug:
-------------------+-------------------------
Changes (by zooko):
* status: new => closed
* resolution: => invalid
Comment:
Ah, our copy of the embedded Crypto++ was never subject to this because we
never yet adopted
[http://bazaar.launchpad.net/~zooko/cryptopp/trunk/revision/486#rijndael.cpp
this patch] which introduced the bug (while adding support for the AES-NI
instruction. Just remember, if we adopt
[http://bazaar.launchpad.net/~zooko/cryptopp/trunk/revision/486#rijndael.cpp
this patch] and then we also need
[http://bazaar.launchpad.net/~zooko/cryptopp/trunk/revision/500#rijndael.cpp
that one].
--
Ticket URL: <http://tahoe-lafs.org/trac/pycryptopp/ticket/76#comment:2>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>
More information about the tahoe-lafs-trac-stream
mailing list