1From dlitz@dlitz.net Sat Feb 28 21:45:09 2009 2Date: Sat, 28 Feb 2009 21:45:09 -0500 3From: "Dwayne C. Litzenberger" <dlitz@dlitz.net> 4To: Barry A Warsaw <barry@python.org> 5Subject: PyCrypto license clarification 6Message-ID: <20090301024509.GA13195@rivest.dlitz.net> 7MIME-Version: 1.0 8Content-Type: text/plain; charset=us-ascii; format=flowed 9Content-Disposition: inline 10User-Agent: Mutt/1.5.16 (2007-06-11) 11Status: RO 12Content-Length: 2535 13 14Hi Barry, 15 16I am the new maintainer of the Python Cryptography Toolkit, and I am 17working on a new release at http://www.pycrypto.org/. 18 19People often ask me what license PyCrypto is covered by, if it's 20GPL-compatible, etc. Right now, I'm not really sure what to tell them. 21The text in the current LICENSE file (quoted below) is not entirely clear 22on the point of whether distributing modified versions is allowed. (It 23says "distribute and use", but not "modify".) 24 25 =================================================================== 26 Distribute and use freely; there are no restrictions on further 27 dissemination and usage except those imposed by the laws of your 28 country of residence. This software is provided "as is" without 29 warranty of fitness for use or suitability for any purpose, express 30 or implied. Use at your own risk or not at all. 31 =================================================================== 32 33 Incorporating the code into commercial products is permitted; you do 34 not have to make source available or contribute your changes back 35 (though that would be nice). 36 37 --amk (www.amk.ca) 38 39For the next PyCrypto release, I would like to take steps to move toward a 40clearer licensing regime. I am asking as many copyright holders as I can 41find if I can release PyCrypto under something clearer and more standard. 42Below, I have quoted a public domain dedication that was recommended in 43_Intellectual Property and Open Source: A Practical Guide to Protecting 44Code_, by Van Lindberg. I have already contacted A. M. Kuchling, Robey 45Pointer, and Wim Lewis, and they have all approved the following dedication 46for their contributions. 47 48I understand that you have made contributions to PyCrypto. May I, on your 49behalf, dedicate to the public domain all your contributions to PyCrypto, 50with the following notice? 51 52 ======================================================================= 53 The contents of this file are dedicated to the public domain. To the 54 extent that dedication to the public domain is not available, everyone 55 is granted a worldwide, perpetual, royalty-free, non-exclusive license 56 to exercise all rights associated with the contents of this file for 57 any purpose whatsoever. No rights are reserved. 58 ======================================================================= 59 60Regards, 61 - Dwayne 62 63-- 64Dwayne C. Litzenberger <dlitz@dlitz.net> 65 Key-signing key - 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7 66 67From barry@python.org Mon Mar 2 11:29:39 2009 68X-Maildir-Dup-Checked: Yes 69Return-Path: <barry@python.org> 70X-Original-To: dwon@rivest.dlitz.net 71Delivered-To: dwon@rivest.dlitz.net 72Received: from goedel.dlitz.net (unknown [10.159.255.6]) 73 by rivest.dlitz.net (Postfix) with ESMTP id 6E01AC6640B 74 for <dwon@rivest.dlitz.net>; Mon, 2 Mar 2009 11:29:39 -0500 (EST) 75Received: from localhost (localhost [127.0.0.1]) 76 by goedel.dlitz.net (Postfix) with QMQP id 0644E1007A 77 for <dwon@rivest.dlitz.net>; Mon, 2 Mar 2009 10:29:39 -0600 (CST) 78Received: (vmailmgr-postfix 8668 invoked by uid 1003); 2 Mar 2009 10:29:39 -0600 79Delivered-To: m-dlitz-dlitz@dlitz.net 80Received-SPF: none (python.org: No applicable sender policy available) receiver=goedel.dlitz.net; identity=mfrom; envelope-from="barry@python.org"; helo=mail.wooz.org; client-ip=216.15.33.230 81Received: from mail.wooz.org (216-15-33-230.c3-0.slvr-ubr2.lnh-slvr.md.static.cable.rcn.com [216.15.33.230]) 82 by goedel.dlitz.net (Postfix) with ESMTP id CCEA110073 83 for <dlitz@dlitz.net>; Mon, 2 Mar 2009 10:29:38 -0600 (CST) 84Received: from snowdog.wooz.org (snowdog.wooz.org [192.168.11.202]) 85 by mail.wooz.org (Postfix) with ESMTPSA id ACE30E3C9F 86 for <dlitz@dlitz.net>; Mon, 2 Mar 2009 11:29:35 -0500 (EST) 87Message-Id: <09BF1A39-B015-4820-97A3-8642490C8254@python.org> 88From: Barry Warsaw <barry@python.org> 89To: Dwayne C. Litzenberger <dlitz@dlitz.net> 90In-Reply-To: <20090301024509.GA13195@rivest.dlitz.net> 91Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes 92Content-Transfer-Encoding: quoted-printable 93Mime-Version: 1.0 (Apple Message framework v930.3) 94Subject: Re: PyCrypto license clarification 95Date: Mon, 2 Mar 2009 11:29:34 -0500 96References: <20090301024509.GA13195@rivest.dlitz.net> 97X-Pgp-Agent: GPGMail d55 (v55, Leopard) 98X-Mailer: Apple Mail (2.930.3) 99Status: RO 100Content-Length: 869 101 102-----BEGIN PGP SIGNED MESSAGE----- 103Hash: SHA1 104 105On Feb 28, 2009, at 9:45 PM, Dwayne C. Litzenberger wrote: 106 107> I am the new maintainer of the Python Cryptography Toolkit, and I am =20= 108 109> working on a new release at http://www.pycrypto.org/. 110 111Great! I'm glad to see someone taking up the mantle of this important =20= 112 113Python library. 114 115> I understand that you have made contributions to PyCrypto. May I, =20 116> on your behalf, dedicate to the public domain all your contributions =20= 117 118> to PyCrypto, with the following notice? 119 120Absolutely yes. 121 122Cheers, 123Barry 124 125-----BEGIN PGP SIGNATURE----- 126Version: GnuPG v1.4.9 (Darwin) 127 128iQCVAwUBSawJbnEjvBPtnXfVAQLZjgP/ecG+JdZwNvPJRfsa6rhY6+MHLDHI6agk 129evkJnSJQAcVHlZnVlVeR5IXgvDUMakZjU4SOV7MqkhsKA9lIet7PaD9VSYgn3ra5 130gElwI2DQDoOy5GExXMm74gqrrb1PCCbCRmpaYNo+DZohwHkeFBjbwDRA3wItOrH7 131SK4w9VBJtfY=3D 132=3DQduY 133-----END PGP SIGNATURE----- 134 135 136