[tahoe-lafs-trac-stream] [pycryptopp] #89: see if we should copy in any of the Crypto++ patches from the 5.6.2 cycle

[pycryptopp]

#89: see if we should copy in any of the Crypto++ patches from the 5.6.2 cycle
-----------------------------+-----------------
     Reporter:  zooko        |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  major        |  Milestone:
      Version:  0.5.29       |   Keywords:
Launchpad Bug:               |
-----------------------------+-----------------
 We are using a copy of Crypto++ which is (if I recall correctly) v5.6.1
 plus a patch or two that was committed to upstream, Crypto++ since then.
 It would be good to review the patches that have been committed to
 Crypto++ upstream since we branched and see if any of them would address
 any known issues in our usage.

 If the Crypto++ SVN isn't working, you can try this web-browseable bzr
 mirror: https://bazaar.launchpad.net/~zooko/cryptopp/trunk/changes/

 That thing is automatically updated by launchpad.net to mirror the latest
 SVN version from sourceforge.net.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/pycryptopp/ticket/89>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>