[tahoe-lafs-trac-stream] [Tahoe-LAFS] #1792: make Tahoe-LAFS work under PyPy

[Tahoe-LAFS]

#1792: make Tahoe-LAFS work under PyPy
----------------------------+----------------------------------------------
     Reporter:  davidsarah  |      Owner:
         Type:  defect      |     Status:  new
     Priority:  normal      |  Milestone:  eventually
    Component:  packaging   |    Version:  1.9.2
   Resolution:              |   Keywords:  pypy cpyext packaging pycryptopp
Launchpad Bug:              |
----------------------------+----------------------------------------------

Comment (by hawkowl):

 That policy sounds reasonable -- although pynacl doesn't expose much more
 than ed22519 keys and "boxes" (Curve25519-pubpriv, salsa20+Poly1305
 symmetric), so, unless the new features use that, you'll have to use
 Cryptography.

 To replace pycryptopp in Tahoe, both Cryptography and pynacl will have to
 be used (pynacl for the ed22519, cryptography for AES, RSA, and SHA-2), so
 new features could possibly rely on either. The best case is that
 Cryptography later comes with a non-OpenSSL backend (that being said,
 LibreSSL works, if I'm not mistaken), which is improbable (because it's a
 lot of work) but possible (because it's been written from the start to
 have multiple backends -- on OS X it uses CommonCrypto for instance).

 I'll see what I can get from a day of hacking in the sprints.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1792#comment:4>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage