pyOpenSSL 0.13

pyOpenSSL is a Python wrapper for a subset of OpenSSL's functionality. It features an advanced error management system, connection objects that wrap socket methods, and flexible context objects.

Also included is a rudimentary crypto module that can be used to create and verify certificates (X509 objects).

Installation:

pyOpenSSL uses distutils, so there really shouldn't be any problems. To build
the library:

python setup.py build

If your OpenSSL header files aren't in /usr/include, you may need to supply the -I flag to let the setup script know where to look. The same goes for the libraries of course, use the -L flag. Note that build won't accept these flags, so you have to run first build_ext and then build! Example:

python setup.py build_ext -I/usr/local/ssl/include -L/usr/local/ssl/lib
python setup.py build

Now you should have a directory called OpenSSL that contains e.g. SSL.so and
__init__.py somewhere in the build dicrectory, so just:

python setup.py install

If you, for some arcane reason, don't want the module to appear in the site-packages directory, use the --prefix option.

You can, of course, do

python setup.py --help

to find out more about how to use the script.

Documentation:

The documentation is written in LaTeX, using the standard Python templates, and tools to compile it into a number of forms are included. You need to supply things like dvips, latex2html yourself of course!

To build the text, html, postscript or dvi forms of the documentation, this is what you do:

cd doc
# To make the text-only documentation:
make text
# To make the dvi form:
make dvi

It's as simple as that. Note that since Python's mkhowto script is used, if you do first ``make dvi'' and then ``make ps'', the dvi file will disappear. I included a special build target ``make all'' that will build all the documentation in an order that won't let anything disappear.

Product's homepage

What's New in This Release: [ read full changelog ]

· This release fixes an incompatibility with Python 2.7 involving memoryviews. It also exposes the "info callback" constants used to report progress of the TLS handshake and later steps of SSL connections. Perhaps most interestingly, it also adds support for inspecting arbitrary X509 extensions.