Here's where the upstream Tahoe-LAFS specifies what version of pycryptopp it needs:
http://tahoe-lafs.org/trac/tahoe- lafs/browser/trunk/src/allmydata/_auto_deps.py?annotate=blame&rev=4976#L64 It says: 64 if platform.machine().lower() in ['i386', 'x86_64', 'amd64', 'x86', '']: 65 # pycryptopp v0.5.20 fixes bugs in SHA-256 and AES on x86 or amd64 66 # (from Crypto++ revisions 470, 471, 480, 492). The '' is there 67 # in case platform.machine is broken and this is actually an x86 68 # or amd64 machine. 69 install_requires.append("pycryptopp >= 0.5.20") 70 else: 71 # pycryptopp v0.5.13 had a new bundled version of Crypto++ 72 # (v5.6.0) and a new bundled version of setuptools (although that 73 # shouldn't make any difference to users of pycryptopp). 74 install_requires.append("pycryptopp >= 0.5.14") So it sounds like it is potentially important to upgrade pycryptopp in Ubuntu from v0.5.17 to v0.5.20. Doing so fixes a bug which causes incorrecvt SHA-256 and AES computations on x86 and amd64 architectures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/782461 Title: too high version dependency on pycryptopp -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
