In a previous hackweek project (https://github.com/SUSE/hackweek/wiki/osc3%3A-port-osc-to-Python3) I have converted osc code to Python3. This has triggered quite some weirdness regarding plugins, but osc is usable from python3. Or it was, not sure if more recent changes did not break the compatibility.
But usable means, you can run osc if you don't need to bother with ssl. Which you need to, so osc3 is barely usable in a real world. osc interfaces with openssl through M2Crypto, which lacks python3 version. At the same time, python3 got much better support for ssl. So task would be to evaluate the most easy way to switch osc's ssl to python3.
There were three possible ways I have had analyzed.
- Use python.ssl module, which would be the most viable approach.
- Check the existence of much better module
- Port M2Crypto to python3
Python ssl module does provide a nice HTTPSConnection classes. But it is mostly incompatible with python 2.6.x ssl module, so one would need to use M2Crypto for python2 and ssl for python3, which would means two codepaths. But the ship stopper was the fact M2Crypto allows to work with X509 certificates stored in
~/.config/osc/trusted-certs/, where I did not find an alternative functionality in ssl module. A short attempt to write own X509 handling code using python-cffi showed me that OpenSSL is much more complex library than one would thing. And with almost no documentation or comments in source code.
I was not successful with a looking for much better ssl module. And there are none as far as I know. The most promising project is https://github.com/pyca/cryptography, but not finished and not dealing with X509 certs. An another opinion was https://github.com/alex/opentls, but it seems more like alex's learning project before contributing to cryptography.
So the last remaining option was to port M2Crypto to Python 3.
I have found the related bug report https://bugzilla.osafoundation.org/show_bug.cgi?id=12853 and realized that Matěj Cepl from RedHat made an initial effort. So I have forked his repository https://github.com/mcepl/m2crypto and made some nice progress, which unfortunately means that all low-hanging fruits are now fixed.
What I learned
- much much much more details about Python3 internals and how it is different from Python2 (especially IO). I can recommend to take a look at http://www.slideshare.net/dabeaz/mastering-python-3-io
- some limited ability to write a code in SWIG
- much much much much more about OpenSSL and how hard is to get into, because of a complexity and lack of docs
- the fact that in a month when last python 2 interpreter release will appear (Oct 2013), there is no good and powerful OpenSSL binding available
This project is part of:
Hack Week 10
[comment]: # (Please use the project descriptio...
Join the Gitter channel! [https://gitter.im/uy...
Deep Packet Inspection: compare the performance between libnetfilter_queue, NF_HOOK and eBPF XDP by nguyens
[comment]: # Deep Packet Inspection: compare th...
OTPClient is currentl...