[tahoe-lafs-trac-stream] [Tahoe-LAFS] #2322: use 'cryptography' instead of 'pycryptopp'

[Tahoe-LAFS]

#2322: use 'cryptography' instead of 'pycryptopp'
-------------------------+-------------------------------------------------
     Reporter:  daira    |      Owner:
         Type:           |     Status:  new
  enhancement            |  Milestone:  undecided
     Priority:  normal   |    Version:  1.10.0
    Component:  code     |   Keywords:  cryptography pycryptopp aes chacha
   Resolution:           |  rsa ed25519
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Description changed by daira:

Old description:

> See http://www.mail-archive.com/cryptopp-
> users%40googlegroups.com/msg06857.html for motivation.
>
> Zooko wrote
> > In the future, I intend to work toward replacing Crypto++ entirely in
> pycryptopp, for reasons of compilation, portability, deployment, etc.
> >
> > The biggest single problem I have with Crypto++ is that it is written
> in C++. Every couple of years this causes a deployment headache for me.
> >
> > The most recent example is that the newest and best way to interface
> native code to Python -- cffi (http://cffi.readthedocs.org/en/latest/)
> doesn't support C++ at all. I think I'd rather have the simplicity of
> using cffi and give up the
> advantages of Crypto++. That means I have to adopt some other
> implementation of AES and of RSA, most likely by relying on a future
> release of pyOpenSSL which is itself based on cffi and which exposes
> the lower-level API of OpenSSL to Python land.

New description:

 See http://www.mail-archive.com/cryptopp-
 users%40googlegroups.com/msg06857.html for motivation.

 Zooko wrote
 > In the future, I intend to work toward replacing Crypto++ entirely in
 pycryptopp, for reasons of compilation, portability, deployment, etc.
 >
 > The biggest single problem I have with Crypto++ is that it is written in
 C++. Every couple of years this causes a deployment headache for me.
 >
 > The most recent example is that the newest and best way to interface
 native code to Python -- cffi (http://cffi.readthedocs.org/en/latest/)
 doesn't support C++ at all. I think I'd rather have the simplicity of
 using cffi and give up the advantages of Crypto++. That means I have to
 adopt some other implementation of AES and of RSA, most likely by relying
 on a future release of pyOpenSSL which is itself based on cffi and which
 exposes the lower-level API of OpenSSL to Python land.

--

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