[Cryptography-dev] First release -- asymmetric?

[Donald Stufft]

I’m personally fine without any asymmetric for the first release with Hynek’s
concern mirrored about wanting to change the symmetric APIs with our
experience in asymmetric.

On Dec 30, 2013, at 6:59 PM, Hynek Schlawack <hs at ox.cx> wrote:

> On 31 Dec 2013, at 0:01, Alex Gaynor wrote:
> 
>> What do people think of the idea of us doing our first release without
>> having any asymmetric support?
>> 
>> The motivation here would be to allow us to get our initial release out
>> sooner, addressing the following concerns:
>> 
>> - pyOpenSSL! (specifically on PyPy)
>> - Crypto on py3k and on PyPy
>> - GCM support
>> - A safe recipe for symmetric encryption.
>> 
>> What do folks think about this idea?
> 
> Actually, why not?  We “just” need to be half-way sure that those points you mentioned don’t change while implementing asymmetric encryption because I’d really not like to break compatibility at any point._______________________________________________
> Cryptography-dev mailing list
> Cryptography-dev at python.org
> https://mail.python.org/mailman/listinfo/cryptography-dev


-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/cryptography-dev/attachments/20131230/169ea63c/attachment.sig>