[Cryptography-dev] Criteria for first release?

Alex Gaynor alex.gaynor at gmail.com
Thu Oct 24 17:27:02 CEST 2013


Hi all!

We're at an exciting point where it's actually possible to do stuff with
cryptography. You know what that means... time to start thinking about a
release! I'd like us to make a list of the stuff we think should be in our
first release. Here's my list:

* Figure out our packaging / bundling story with OpenSSL
* Finish binding OpenSSL to the point where JP can use it for PyOpenSSL
* The last two block ciphers that conch would need (CAST and Blowfish)
* Finalizing the iterator APIs for BlockCipher
* Padding APIs

Here's stuff I'm not sure about:
* Everything that conch needs (this means figuring out the API for RSA/DSA)
* GCM
* CommonCrypto backend

What do ya'll think, am I missing anything, do I have to much?

As a heads up: once we're ready to do the release and we've frozen a
release-candidate I plan to investigate getting it audited.

Alex

-- 
"I disapprove of what you say, but I will defend to the death your right to
say it." -- Evelyn Beatrice Hall (summarizing Voltaire)
"The people's good is the highest law." -- Cicero
GPG Key fingerprint: 125F 5C67 DFE9 4084
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20131024/d198e466/attachment.html>


More information about the Cryptography-dev mailing list