pycryptopp: a small number of good cryptography algorithms
Introduction and Licence
pycryptopp is a python wrapper around a few algorithms from the Crypto++ and python-Ed25519 libraries.
It lives at https://tahoe-lafs.org/trac/pycryptopp
LICENCE
You may use this package under the GNU General Public License, version 2 or, at your option, any later version. You may use this package under the Transitive Grace Period Public Licence, version 1.0 or, at your option, any later version. (You may choose to use this package under the terms of either licence, at your option.) See the file COPYING.GPL for the terms of the GNU General Public License, version 2. See the file COPYING.TGPPL.html for the terms of the Transitive Grace Period Public Licence, version 1.0.
The Ed25519 code comes from the python-ed25519 distribution ¹, for which the basic C code is in the public domain, and the Python bindings are under the MIT license. See COPYING.ed25519 for details.
BUILDING
To build it run “./setup.py build”. To test it run “./setup.py test”. To install it into your system run “./setup.py install”. To create a binary package run “./setup.py bdist_egg”.
If “./setup.py test” doesn’t print out “PASSED” and exit with exit code 0 then there is something seriously wrong. Do not use this build of pycryptopp. Please report the error to the tahoe-dev mailing list ².
DOCUMENTATION
The documentation is in the docstrings. From a command-line, use “pydoc pycryptopp”, “pydoc pycryptopp.cipher”, and so on. From within a Python interpreter use “help(pycryptopp)”, “help(pycryptopp.cipher)”, “help(pycryptopp.cipher.aes)” and so on.
The documentation for pycryptopp.publickey.ed25519 is in README.ed25519, adapted from the upstream python-ed25519 library.
CONTACT
Please post to the tahoe-dev mailing list ² with comments about this package.
BOOK REVIEW
If you are not already acquainted with how to use modern cryptography, buy a copy of Ferguson, Schneier, and Kohno “Cryptography Engineering” and read it. It is easy going and will increase your understanding greatly.
ACKNOWLEDGEMENTS
Thanks to Wei Dai and the contributors to Crypto++, Andrew M. Kuchling for his “pycrypto” library which inspired this one, Brian Warner for help on Python packaging questions, python-Ed25519, inspiration, and a million other things besides, Greg Hazel and Samuel Neves for Windows porting and fixing bugs, and Daniel J. Bernstein for Ed25519.
Zooko Wilcox-O’Hearn
Santa Clara, California, USA
2012-03-12
Metadata
Release files for pycryptopp 0.6.0.1206569328141510525648634803928199668821045408958
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958.tar.gz | 2.0 MB | Without provenance | Details for pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958.tar.gz |
Release files / pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958.tar.gz
| Download URL | pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
116158917bd243da2701cfeba9a6374854bc9a599d1466e1a2dbadf37c802059
|
|
BLAKE2b-256 checksum How to use checksums |
bd6b5845a594602ef5274826a8a54ef8760530fb1c4a3e0f6d13490ea89e2a2f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pycryptopp 0.6.0.1206569328141510525648634803928199668821045408958
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.