[change] Drop pyOpenSSL in favour of cryptography

[davidjmemmett]

Hi,

I've just started playing around with django-x509, and it does exactly what is says on the tin; thank you very much for providing this library!

I'd like to be able to specify multiple OUs for certificates, however this does not appear to be supported by pyOpenSSL. In addition, pyOpenSSL has been deprecated for some time by the maintainers and recommends that users migrate over to the cryptography library, which incidentally does support multiple OUs.

[davidjmemmett]

(Before anybody suggests it, I'm not part of any hacktoberfest malarkey, I'm an actual user of this library!)

[nemesifier]

@davidjmemmett thanks for reporting this, we are not aware of the deprecation, can you point out in which communication was this information published by pyOpenSSL?
As long as we maintain backward compatibility I don't see a problem in migrating to the cryptography lib if that's the way to go for the future.

[davidjmemmett]

Hi @nemesisdesign,

As per the opening paragraph on pyOpenSSL's README, and according to the history of said file, it's been deprecated since ~16th May 2018.

[nemesifier]

I think PRs are welcome on this. Sooner or later we'll have to upgrade.

[nemesifier]

I tried dedicating 1 hour to this task but it's clearly not enough and my knowledge of cryptography is not enough to do this quickly. #178 is up but it clearly needs more work. If anyone wants to contribute let me know I will give you write access (in the meantime you can work on it in your own fork).

[davidjmemmett]

Thank you for your efforts, happy to take a look over it all at some point - possibly in a couple of weeks time.