[pyOpenSSL-Users] Announcing pyOpenSSL 0.14a2

[Deni Bertović]

This is the best news I've read this year! :)

Thank you all for your efforts.

-Deni


On Thu, Jan 16, 2014 at 1:41 PM, <exarkun at twistedmatrix.com> wrote:

> Hello all,
>
> I'm happy to announce that pyOpenSSL 0.14a2, the second alpha of the 0.14
> release cycle, is now available.
>
> A copy of these release notes and links to source archive downloads are
> available at <https://github.com/pyca/pyopenssl/releases/tag/0.14a2>.
>
> pyOpenSSL 0.14 will bring many improvements over the previous release,
> including:
>
>  * Support for TLSv1.1 and TLSv1.2
>  * New flags, such as MODE_RELEASE_BUFFERS and OP_NO_COMPRESSION
>  * Some APIs to access to the SSL session cache
>  * A variety of bug fixes for error handling cases
>
> Additionally, there are three major changes to the project:
>
> First, the documentation has been converted from LaTeX (CPython's old
> documentation system) to Sphinx (CPython's new documentation system ;).
>
> Second, pyOpenSSL is no longer implemented in C as a collection of
> extension modules using the Python/C API.  Instead, pyOpenSSL is now a
> pure-Python project with a dependency on a new project, <
> http://github.com/pyca/cryptography>, which provides (among other things)
> a cffi-based interface to OpenSSL.
>
> This change means that pyOpenSSL development is now more accessible to
> Python programmers with little or no experience with C.
>
> Finally, the project's code hosting has moved from Launchpad to Github.
> Many branches remain only on Launchpad along with their associated bug
> reports.  Over the coming releases I hope that the fixes and features in
> these branches will be ported to Python and incorporated into the pyOpenSSL
> master development branch.  Bug tracking has been disabled on Launchpad so
> that the amount of useful information hosted there can gradually dwindle to
> nothing.  Please use Github for further development and bug reporting.
>
> As you might imagine, reimplementing all of pyOpenSSL in a new language
> has involved far more significant changes than I have ever included in a
> pyOpenSSL release before.  I've also bent my own rule of not modifying
> untested code a bit.  Because certain OpenSSL error cases are very
> difficult to trigger reliably (or even unreliably in some cases), not all
> such cases are covered by the automated test suite.  In the past I've tried
> hard to avoid changing these parts of pyOpenSSL but that wasn't an option
> for this release.
>
> As such, testing of 0.14a2 is more important than ever before.  Please do
> whatever you can to help out here.  Run your test suite against it, play
> around with the new features, abuse it if you can, take a look at the
> implementation (the wonderful, wonderful Python implementation!), share
> this release announcement in other forums where it may be relevant, and
> anything else you can think of!
>
> Any reports of your results are appreciated, positive or negative.
>
> Thanks to all,
> Jean-Paul
> _______________________________________________
> pyopenssl-users mailing list
> pyopenssl-users at python.org
> https://mail.python.org/mailman/listinfo/pyopenssl-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pyopenssl-users/attachments/20140128/fda45bd1/attachment.html>