** Changed in: pycrypto
Milestone: None => 2.1.0
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
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
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You rece
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.
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You received this bug notifica
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: (unassigned) => Dwayne Lit
fixed in intrepid
re hardy: I don't care that much; I accidentally opened the task for
hardy.
** Changed in: python-crypto (Ubuntu)
Status: New => Fix Released
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You received thi
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
--
pycrypto's SHA256 gives wrong answers
already fixed in hardy
** Changed in: python-crypto (Ubuntu Hardy)
Status: New => Invalid
--
pycrypto's SHA256 gives wrong answers if input block length % 56 is 0
https://bugs.launchpad.net/bugs/191683
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
