[Twisted-Python] Announcing pyOpenSSL 0.14a3
Hello all, I'm happy to announce the third alpha leading up to the release of pyOpenSSL 0.14. pyOpenSSL is the library Twisted uses for all of its SSL functionality. pyOpenSSL 0.14 is bringing some major changes compared to pyOpenSSL 0.13. Any and all testing is greatly appreciated. You can read more about the changes and download the source tarball from the github release page: https://github.com/pyca/pyopenssl/releases/tag/0.14a3 Feel free to leave feedback here, on a github issue, or on the pyOpenSSL mailing list. Thanks! Jean-Paul
Hi JP, FWIW, clarent appears to work fine against twisted and pyopenssl trunk. Is there a significant difference between the alpha and trunk (so that I should also test against the alpha specifically)? merlyn blows up, but that appears to be only because Axiom uses unsignedID, which has been removed from twisted apparently :) hth lvh
On 12:44 pm, _@lvh.io wrote:
Hi JP,
FWIW, clarent appears to work fine against twisted and pyopenssl trunk. Is there a significant difference between the alpha and trunk (so that I should also test against the alpha specifically)?
merlyn blows up, but that appears to be only because Axiom uses unsignedID, which has been removed from twisted apparently :)
Hi Laurens, Right now pyOpenSSL trunk and the release branch only differ in the version number they report. There are some important differences between a2 and a3 though (so if you tested trunk before I announced a3 you might not have tested the latest code - of course, I hope those changes only fixed things, not introduced any new bugs ;). Thanks! Jean-Paul
On Tue, Jan 21, 2014 at 2:26 PM, <exarkun@twistedmatrix.com> wrote:
Hi Laurens,
Right now pyOpenSSL trunk and the release branch only differ in the version number they report. There are some important differences between a2 and a3 though (so if you tested trunk before I announced a3 you might not have tested the latest code - of course, I hope those changes only fixed things, not introduced any new bugs ;).
Yep, I've been testing against trunk pretty much continuously over the last few days, so I think we're good. Anyway, all systems green AFAICT, at least no PyOpenSSL bugs.. cheers lvh
On Tue, Jan 21, 2014 at 12:22:41PM -0000, exarkun@twistedmatrix.com wrote:
Hello all,
I'm happy to announce the third alpha leading up to the release of pyOpenSSL 0.14.
pyOpenSSL is the library Twisted uses for all of its SSL functionality.
pyOpenSSL 0.14 is bringing some major changes compared to pyOpenSSL 0.13. Any and all testing is greatly appreciated.
I'm glad to see the new documentation will finally show up! Jonathan
On 01:25 pm, jon@multani.info wrote:
On Tue, Jan 21, 2014 at 12:22:41PM -0000, exarkun@twistedmatrix.com wrote:
Hello all,
I'm happy to announce the third alpha leading up to the release of pyOpenSSL 0.14.
pyOpenSSL is the library Twisted uses for all of its SSL functionality.
pyOpenSSL 0.14 is bringing some major changes compared to pyOpenSSL 0.13. Any and all testing is greatly appreciated.
I'm glad to see the new documentation will finally show up!
Indeed. :) Sorry about the long delay in publishing this and thank you for doing the conversion. :) Jean-Paul
Thanks for working on this! Do you know if there are binary eggs for Windows Python 2.7 32bit for criptography and cffi ? This would make testing easier for people like me who don't have a Windows development environment but have access to a default installation of Windows. A package containing OpenSSL as in previous pyOpenSSL distributions for Windows would be of great help. I noticed that the new API no longer accepts unicode strings. As long as it does not touches the OS filesystem this should be fine. I checked the tests for Context.load_verify_locations() and I see that there is no test for Unicode paths. Linux filesystem access will accept any file name and works with UTF-8 encoded byte strings. I have tested this and it works. But I remember that on Windows for paths containing unicode chars you always need to pass the path as Unicode. Maybe this is not a problem since filesystem access is handled by OpenSSL and not by Python -------- No problems with HTTPS support on Twisted 12.2, but I have only basic usage. I have tested the new pyOpenSSL with my messy Implicit and Explicit FTPS implementation and there was a single major problem with Context.set_info_callback.. I have reported all problems in GitHub. Thanks! On 21 January 2014 15:32, <exarkun@twistedmatrix.com> wrote:
On 01:25 pm, jon@multani.info wrote:
On Tue, Jan 21, 2014 at 12:22:41PM -0000, exarkun@twistedmatrix.comwrote:
Hello all,
I'm happy to announce the third alpha leading up to the release of pyOpenSSL 0.14.
pyOpenSSL is the library Twisted uses for all of its SSL functionality.
pyOpenSSL 0.14 is bringing some major changes compared to pyOpenSSL 0.13. Any and all testing is greatly appreciated.
I'm glad to see the new documentation will finally show up!
Indeed. :) Sorry about the long delay in publishing this and thank you for doing the conversion. :)
Jean-Paul
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
-- Adi Roiban
On 02:03 pm, adi@roiban.ro wrote:
Thanks for working on this!
Thanks for the feedback!
Do you know if there are binary eggs for Windows Python 2.7 32bit for criptography and cffi ?
I've asked the cryptography team about this. Apparently not yet, but I reminded them Windows users would have a pretty hard time benefiting from any of this work until there is a binary Windows distribution. Thanks for the bug reports. I'll respond to those in the issue tracker in due time. :) Jean-Paul
participants (4)
-
Adi Roiban -
exarkun＠twistedmatrix.com -
Jonathan Ballet -
Laurens Van Houtven