Python Shell
Clone or download
Failed to load latest commit information.
.travis We don't need the whole history. Mar 16, 2016
doc Fixed a handful of typos (#755) May 14, 2018
examples fix errors with latest flake8 (#710) Nov 20, 2017
leakcheck Switch to an explicit curve object. Apr 19, 2014
rpm ps make target doesn't exist anymore in the new doc Makefile May 26, 2015
src/OpenSSL Only allocate exponent in the TYPE_RSA path. (#767) Jun 5, 2018
tests fix wantWriteError to error even with big socket buffers (#782) Aug 9, 2018
.coveragerc Run coverage over the tests (#504) Jul 6, 2016
.gitignore Move package into src Oct 17, 2015
.mention-bot Added a mentionbot blacklist in prep for enabling it (#510) Jul 31, 2016
.travis.yml Added py37 (#772) Jul 4, 2018
CHANGELOG.rst reopen master for 18.1 (#761) May 16, 2018
CODE_OF_CONDUCT.rst Adopt CoC Covenant Mar 17, 2016
CONTRIBUTING.rst Fix up some pytest-related stuff (#601) Feb 18, 2017
INSTALL.rst Add an informative (#620) May 13, 2017
LICENSE Get rid of the old copyright file, drop in a new one with the APL2. Mar 3, 2011 make codecov stop commenting (#756) May 14, 2018
README.rst tell people to stop using this where possible (#759) May 16, 2018
codecov.yml make codecov stop commenting (#756) May 14, 2018
setup.cfg Raise minimum cryptography version to 2.2.1, drop python 2.6 (#742) Mar 21, 2018 Fixes #784 -- bump minimum cryptography version (#785) Aug 10, 2018
tox.ini Fixes #784 -- bump minimum cryptography version (#785) Aug 10, 2018


pyOpenSSL -- A Python wrapper around the OpenSSL library

Stable Docs Build status Test coverage

Note: The Python Cryptographic Authority strongly suggests the use of pyca/cryptography where possible. If you are using pyOpenSSL for anything other than making a TLS connection you should move to cryptography and drop your pyOpenSSL dependency.

High-level wrapper around a subset of the OpenSSL library. Includes

  • SSL.Connection objects, wrapping the methods of Python's portable sockets
  • Callbacks written in Python
  • Extensive error-handling mechanism, mirroring OpenSSL's error codes

... and much more.

You can find more information in the documentation. Development takes place on GitHub.


If you run into bugs, you can file them in our issue tracker.

We maintain a cryptography-dev mailing list for both user and development discussions.

You can also join #cryptography-dev on Freenode to ask questions or get involved.