> On 28 Jun 2016, at 17:24, Nikolaus Rath <nikol...@rath.org> wrote: > > I don't understand why everyone using it would have to re-implement the > same functionality. Would you be interested in a patch that adds this to > pyOpenSSL?
We would not, for two reasons. Firstly, PyOpenSSL’s stated goal is of being a thin wrapper around OpenSSL’s APIs, rather than the full OpenSSL abstraction layer that the stdlib ssl module (claims to) implement. Secondly, PyOpenSSL is now in maintenance mode: we’re aiming to slowly transition users to cryptography.io as it becomes more fully-featured and able to replace PyOpenSSL. We will still fix bugs and and will resolve glaring holes in features that cryptography does not have, but otherwise we’ve got a ‘no new features’ policy. Cory
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev