Changes between Initial Version and Version 1 of Ticket #2322


Ignore:
Timestamp:
2014-10-17T10:41:39Z (10 years ago)
Author:
daira
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2322 – Description

    initial v1  
    44> In the future, I intend to work toward replacing Crypto++ entirely in pycryptopp, for reasons of compilation, portability, deployment, etc.
    55>
    6 > 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
    7 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
     6> 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.
     7>
     8> 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
    89advantages 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
    910the lower-level API of OpenSSL to Python land.