Dwayne C. Litzenberger
dlitz at DLITZ.NET
Thu Aug 21 19:01:56 CEST 2008
On Thu, Aug 21, 2008 at 01:19:36PM +0300, Ali Polatel wrote:
>We have a bug¹ about the pycrypto licence being wrong in our repository.
>The tarball states the source is public domain and the sourceforge page
>says it's cnri python.
>Which one is correct? I assume the one in the tarball is the correct one
>but I just want to be sure.
[PyCrypto has its own mailing list now. See http://www.pycrypto.org/.
Please send any replies to that list.]
I've filed a bug in PyCrypto's bug tracker:
The PyCrypto licensing status is a bit of a mess. It looks like a bunch of
reference implementations were simply copied-and-pasted into the source
tree, and each has its own licensing statement.
I recommend looking at each source file and making a judgment for yourself.
I'm slowly working on a new release of PyCrypto (I've just taken over from
Andrew Kuchling). In the next release, I'll try to document things better,
and fix the most obvious problems (I've already written a replacement for
However, some of the software is unattributed. I assume that most of it
was written by A.M. Kuchling, but I can't be totally sure. I'll try to
contact Andrew and see if he can clear things up.
Dwayne C. Litzenberger <dlitz at dlitz.net>
Key-signing key - 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7
Annual key (2008) - 4B2A FD82 FC7D 9E38 38D9 179F 1C11 B877 E780 4B45
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: Digital signature
More information about the python-crypto