pycrypto's SHA256 gives wrong answers if input block length % 56 is 0

Bug #191683 reported by Zooko Wilcox-O'Hearn
2
Affects Status Importance Assigned to Milestone
Python-Crypto
Fix Released
Undecided
Darsey Litzenberger
python-crypto (Ubuntu)
Fix Released
Undecided
Unassigned
Hardy
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: python-crypto

original bug report:

https://bugs.launchpad.net/python-crypto/+bug/131503

patch that fixes this bug:

http://codebrowse.launchpad.net/~robey/pycrypto/devel/revision/294

Revision history for this message
Matthias Klose (doko) wrote :

already fixed in hardy

Changed in python-crypto:
status: New → Invalid
Revision history for this message
Zooko Wilcox-O'Hearn (zooko) wrote :

Do you mean that you applied the patch to the Hardy version of pycrypto? Did you also fix it in Debian? Or did upstream pycrypto maintainer fix it and I didn't notice?

Thanks!

Also, shouldn't this be marked "fixed" instead of "invalid"?

Regards,

Zooko

Revision history for this message
Matthias Klose (doko) wrote :

fixed in intrepid

re hardy: I don't care that much; I accidentally opened the task for hardy.

Changed in python-crypto:
status: New → Fix Released
Revision history for this message
Darsey Litzenberger (dlitz) wrote :

This fix was committed a while ago (before I started maintaining PyCrypto), but here's the change in the git repository: http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.0.x.git;a=commitdiff;h=b41b1e021bd53772f712335de5c6eb8488fd08c5

Changed in pycrypto:
assignee: nobody → dlitz
status: New → Fix Committed
Revision history for this message
Zooko Wilcox-O'Hearn (zooko) wrote :

So, just for the record, if someone is using pycrypto on hardy, are they susceptible to this bug? I'm not sure whether the fix made it into hardy or not.

Revision history for this message
Darsey Litzenberger (dlitz) wrote :

We believe this bug has been fixed in PyCrypto v2.1.0, which can be obtained from http://www.pycrypto.org/

Changed in pycrypto:
status: Fix Committed → Fix Released
Changed in pycrypto:
milestone: none → 2.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.