<div dir="ltr">please keep the DES3 and XOR.<br>we use them and need them in our ongoing projects<br><br><div class="gmail_quote">On Wed, Apr 22, 2009 at 8:23 PM, Jean-Paul Calderone <span dir="ltr"><<a href="mailto:exarkun@twistedmatrix.com">exarkun@twistedmatrix.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br>
<br>
Someone pointed out that XOR and several other ciphers [1] have been<br>
removed from PyCrypto. This has the consequence that Twisted Conch,<br>
and SSH client and server implementation which depends on PyCrypto,<br>
no longer works with the latest development version of PyCrypto, and<br>
I assume that when the next release of PyCrypto is made, Conch also<br>
won't work with that.<br>
<br>
I'm curious how important backwards compatibility is deemed with the<br>
new PyCrypto development going on. A change like the one referenced<br>
above is going to break users of PyCrypto (and that seems like it is<br>
really obvious, to me - as opposed to a change which only accidentally<br>
breaks applications). The added maintenance burden this causes makes<br>
PyCrypto less attractive (one nice thing about PyCrypto having been<br>
unmaintained for a long time is that Conch's use of it stayed as<br>
correct (or incorrect) as it was when it was written). Basically, the<br>
question is whether I should expect more PyCrypto changes like this<br>
as development proceeds, or whether I can make the argument that backwards<br>
compatibility is a *good* thing compelling.<br>
<br>
Of course it's one thing to say "more backwards compatibility please".<br>
Actually deciding how that can be accomplished while allowing development<br>
to proceed in a useful direction is another. However, I'm intentionally<br>
omitting details of that discussion from this message to keep things<br>
simple. I'm convinced that some degree of backwards compatibility is<br>
always possible, regardless of the changes desired, so the details of how<br>
it works aren't as important as deciding whether backwards compatibility<br>
will be maintained.<br>
<br>
So, what do you say? Can we decide that backwards compatibility is a good<br>
thing?<br>
<br>
Jean-Paul<br>
<br>
[1] - <a href="http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.x.git;a=commit;h=5b5b496c0f81f3595d0aebb8da5196492abae429" target="_blank">http://gitweb.pycrypto.org/?p=crypto/pycrypto-2.x.git;a=commit;h=5b5b496c0f81f3595d0aebb8da5196492abae429</a><br>
_______________________________________________<br>
pycrypto mailing list<br>
<a href="mailto:pycrypto@lists.dlitz.net">pycrypto@lists.dlitz.net</a><br>
<a href="http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto" target="_blank">http://lists.dlitz.net/cgi-bin/mailman/listinfo/pycrypto</a><br>
</blockquote></div><br></div>