#2322 closed enhancement (duplicate)

use 'cryptography' instead of 'pycryptopp'

Reported by: daira Owned by:
Priority: normal Milestone: undecided
Component: code Version: 1.10.0
Keywords: cryptography pycryptopp aes chacha rsa ed25519 Cc:
Launchpad Bug:

Description (last modified by daira)

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.

Change History (4)

comment:1 Changed at 2014-10-17T10:41:39Z by daira

  • Description modified (diff)

comment:2 Changed at 2014-10-17T10:42:27Z by daira

  • Description modified (diff)

comment:3 Changed at 2014-10-17T11:08:02Z by daira

This would probably help with #1792.

comment:4 Changed at 2019-07-25T13:10:45Z by exarkun

  • Resolution set to duplicate
  • Status changed from new to closed

ticket:3031 was a duplicate of this and was recently fixed.

Note: See TracTickets for help on using tickets.