#76 closed defect (invalid)
segfault when using embedded Crypto++ on x86_64, assembly disabled, and no AESNI
| Reported by: | zooko | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.6.0 |
| Version: | 0.5.29 | Keywords: | |
| Cc: | Launchpad Bug: |
Description
According to:
http://sourceforge.net/apps/trac/cryptopp/ticket/6
Nobody has reported this against pycryptopp but we should be subject to it.
Change History (3)
comment:1 Changed at 2011-12-23T06:21:25Z by zooko
comment:2 Changed at 2011-12-23T06:59:39Z by zooko
- Resolution set to invalid
- Status changed from new to closed
Ah, our copy of the embedded Crypto++ was never subject to this because we never yet adopted this patch which introduced the bug (while adding support for the AES-NI instruction. Just remember, if we adopt this patch and then we also need that one.
Version 0, edited at 2011-12-23T06:59:39Z
by zooko
(next)
comment:3 Changed at 2012-03-13T07:50:15Z by zooko
- Milestone set to 0.6.0
Note: See
TracTickets for help on using
tickets.
There was previously a ticket on this trac -- #66 -- tracking this bug in the upstream Crypto++, but we also need to fix it in the embedded copy of Crypto++.