Since this came up again on the mailing list: How does this play with the moratorium on new ciphers (http://lists.dlitz.net/pipermail/pycrypto/2010q3/000264.html)? It's not, strictly speaking, a new cipher, and Legrandin has a history of working on the RSA/DSA code. He patched in unit tests, too, which is great.
I'd like to see this resurrected and brought in. I'll even volunteer to bring it into pycrypto-next, though for selfish reasons, I'd like to see the py3k work land on trunk first, then create a branch to bring this patch in. That'd make it easier to maintain one code base. The py3k work and this patch both have a large number of changes to the same files, which would be a pain to merge from two branches.
Since this came up again on the mailing list: How does this play with the moratorium on new ciphers (http:// lists.dlitz. net/pipermail/ pycrypto/ 2010q3/ 000264. html)? It's not, strictly speaking, a new cipher, and Legrandin has a history of working on the RSA/DSA code. He patched in unit tests, too, which is great.
I'd like to see this resurrected and brought in. I'll even volunteer to bring it into pycrypto-next, though for selfish reasons, I'd like to see the py3k work land on trunk first, then create a branch to bring this patch in. That'd make it easier to maintain one code base. The py3k work and this patch both have a large number of changes to the same files, which would be a pain to merge from two branches.