[pycrypto] RSA exportKey() changes set in stone for 2.7?

Kurt Vogel kvogel at mdcom.com
Mon Sep 30 22:28:20 PDT 2013

Hi Dwayne,

Thanks, that is what I was assuming.  If we move import/export to Crypto.IO
it will break backwards compatibility, no?  Is that important?

Is anyone working on this issue?  If backwards compatibility is important I
say keep what we have there now (2.6) and have a deprecation comment and/or
stderr output?

Also does Pycrypto have deprecation/error transition plan?  To ease
transition some packages first do a deprecation warning, second major
release it becomes an error/exception, then third major release the code is
completely removed.  Would that work with pycrypto users?

Your thoughts?

On Sun, Sep 29, 2013 at 6:52 PM, Dwayne Litzenberger <dlitz at dlitz.net>wrote:

> On Wed, Jul 17, 2013 at 01:33:41AM -0700, Kurt Vogel wrote:
>> Hi, quick question for the group and maintainer...
>> I am about ready to deploy a project and wondering how set we are on the
>> format of rsa.exportKey() for next pycrypto?
>> Is it safe to include in our requirements.pip (for now) a reference to
>> https://github.com/dlitz/**pycrypto <https://github.com/dlitz/pycrypto>master branch?  And export my keys with
>> the new protection scheme?  And consequently matching importKey().
>> It would be super nice if we could add **kwargs for iteration_count and
>> salt_size to export() but beggars can't be choosers :)  It seems a simple
>> enough change and looks like importKey() reads those fields in, I'd do it
>> myself but would like any thoughts/opinions?
> Hi Kurt,
> The exportKey API should be considered experimental at this point.  There
> are things about it that don't really make sense (e.g. the `pkcs=1`
> parameter, which doesn't make any sense if you want to expoer in OpenPGP
> format, for example).  Realistically, it should probably be removed from
> Crypto.PublicKey and placed into Crypto.IO, but I'm not sure of exactly
> when that will happen.
> Cheers,
> - Dwayne
> --
> Dwayne C. Litzenberger <dlitz at dlitz.net>
>  OpenPGP: 19E1 1FE8 B3CF F273 ED17  4A24 928C EC13 39C2 5CF7
> ______________________________**_________________
> pycrypto mailing list
> pycrypto at lists.dlitz.net
> http://lists.dlitz.net/cgi-**bin/mailman/listinfo/pycrypto<http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dlitz.net/pipermail/pycrypto/attachments/20130930/9e1919b9/attachment.html>

More information about the pycrypto mailing list