[Cryptography-dev] PyCA cryptography 0.5 release criteria

[Paul Kehrer]

I’m pleased to say that we’ll soon be able to close the final issues that are currently tagged for 0.5. (https://github.com/pyca/cryptography/issues?milestone=5&state=open) If there are any issues you think we should consider a blocker please let me know!

This upcoming release significantly changes the API for asymmetric operations with RSA and DSA, as well as adding major new features like EC support, CFB8 mode, HKDFExpand, AES CTR mode on OpenSSL 0.9.8, some early asymmetric key serialization support, and the usual smorgasbord of code and testing improvements.

One item that still needs some attention is...

Include OpenSSL in our Windows wheels (https://github.com/pyca/cryptography/issues/1121)

The consensus in the issue (thus far) appears to be that we should statically link OpenSSL in our Windows wheels. This would greatly improve the user experience for Windows users at the cost of additional administrative overhead (new releases when OpenSSL does a release, security advisories for OpenSSL vulnerabilities in versions we have linked). Please weigh in with your thoughts!

Thanks to everyone for their help so far this release cycle. This project would not exist without you.

-Paul


1. The previous API, in accordance with our stated deprecation policy (https://cryptography.io/en/latest/api-stability/#deprecation) will continue to work, but emit deprecation warnings.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20140627/f9e4fa0a/attachment.html>