1From dlitz@dlitz.net Sat Feb 28 23:24:14 2009 2Date: Sat, 28 Feb 2009 23:24:14 -0500 3From: "Dwayne C. Litzenberger" <dlitz@dlitz.net> 4To: Jeethu Rao <jeethurao@gmail.com> 5Subject: PyCrypto license clarification 6Message-ID: <20090301042414.GA15122@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: 2513 13 14Hi Jeethu, 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 text for 46their 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 jeethurao@gmail.com Sun Mar 8 17:28:16 2009 68X-Maildir-Dup-Checked: Yes 69Return-Path: <jeethurao@gmail.com> 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 0CC83515D9 74 for <dwon@rivest.dlitz.net>; Sun, 8 Mar 2009 17:28:16 -0400 (EDT) 75Received: from localhost (localhost [127.0.0.1]) 76 by goedel.dlitz.net (Postfix) with QMQP id 4E58F450CB 77 for <dwon@rivest.dlitz.net>; Sun, 8 Mar 2009 15:28:15 -0600 (CST) 78Received: (vmailmgr-postfix 5011 invoked by uid 1003); 8 Mar 2009 15:28:15 -0600 79Delivered-To: m-dlitz-dlitz@dlitz.net 80Received-SPF: pass (gmail.com ... _spf.google.com: 209.85.198.249 is authorized to use 'jeethurao@gmail.com' in 'mfrom' identity (mechanism 'ip4:209.85.128.0/17' matched)) receiver=goedel.dlitz.net; identity=mfrom; envelope-from="jeethurao@gmail.com"; helo=rv-out-0708.google.com; client-ip=209.85.198.249 81Received: from rv-out-0708.google.com (unknown [209.85.198.249]) 82 by goedel.dlitz.net (Postfix) with ESMTP id 3C097449E7 83 for <dlitz@dlitz.net>; Sun, 8 Mar 2009 15:28:12 -0600 (CST) 84Received: by rv-out-0708.google.com with SMTP id k29so1252333rvb.26 85 for <dlitz@dlitz.net>; Sun, 08 Mar 2009 14:27:56 -0700 (PDT) 86DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 87 d=gmail.com; s=gamma; 88 h=domainkey-signature:mime-version:received:in-reply-to:references 89 :date:message-id:subject:from:to:content-type; 90 bh=YWy9U32WCU/ksRqukHwaOZyJQBUs4Yvt5mI20U6mI/g=; 91 b=oMjI22lIxYiJKge2zNJW3rRiUi9LqFXmey5Wp0pLItuNF+X3duyfhopTuBAKw7MwVY 92 B5E6VQuGVEyzBbNsctyVgq6DhQiQtouCLZymSViobmuDmKn5DtUKoxpDk0xCxQmHYaas 93 L9/A6D3/J66kKrNBgX9mc0GPcZTviVFYkPR0Q= 94DomainKey-Signature: a=rsa-sha1; c=nofws; 95 d=gmail.com; s=gamma; 96 h=mime-version:in-reply-to:references:date:message-id:subject:from:to 97 :content-type; 98 b=Ym7CStuDEfJKay1AJyWZkZmJA1lnTcwCG6akBHAXLld8ht6PFcmlsffzZG8hJCIVJ8 99 vljqcT+G6cywVTBw1pyGX7ECYzr0+vhGvgdpACGrs24zikHfpSSd5GFogzXaLVvGVH8p 100 bqSHpfWKKtEP4gAQkiNeIq1GNtR2j8U3fnRyg= 101MIME-Version: 1.0 102Received: by 10.141.176.13 with SMTP id d13mr2656028rvp.231.1236547674677; 103 Sun, 08 Mar 2009 14:27:54 -0700 (PDT) 104In-Reply-To: <20090301042414.GA15122@rivest.dlitz.net> 105References: <20090301042414.GA15122@rivest.dlitz.net> 106Date: Mon, 9 Mar 2009 02:57:54 +0530 107Message-ID: <e3c0ddba0903081427p3a7b1058g417dd8624df68d6d@mail.gmail.com> 108Subject: Re: PyCrypto license clarification 109From: Jeethu Rao <jeethurao@gmail.com> 110To: "Dwayne C. Litzenberger" <dlitz@dlitz.net> 111Content-Type: multipart/alternative; boundary=000e0cd209d0e5a3d40464a23054 112Status: RO 113Content-Length: 7668 114 115--000e0cd209d0e5a3d40464a23054 116Content-Type: text/plain; charset=ISO-8859-1 117Content-Transfer-Encoding: 7bit 118 119Hi Dwayne,My contribution to pycrypto are very very minimal (The sha256 120module, IIRC). 121I'd be fine with the public domain license for PyCrypto. 122 123Jeethu Rao 124PS: Apologies for the delay in my response. 125I don't really check this email address all that often, 126please direct any further correspondence to jeethu@jeethurao.com 127 128On Sun, Mar 1, 2009 at 9:54 AM, Dwayne C. Litzenberger <dlitz@dlitz.net>wrote: 129 130> Hi Jeethu, 131> 132> I am the new maintainer of the Python Cryptography Toolkit, and I am 133> working on a new release at http://www.pycrypto.org/. 134> 135> People often ask me what license PyCrypto is covered by, if it's 136> GPL-compatible, etc. Right now, I'm not really sure what to tell them. The 137> text in the current LICENSE file (quoted below) is not entirely clear on the 138> point of whether distributing modified versions is allowed. (It says 139> "distribute and use", but not "modify".) 140> 141> =================================================================== 142> Distribute and use freely; there are no restrictions on further 143> dissemination and usage except those imposed by the laws of your 144> country of residence. This software is provided "as is" without 145> warranty of fitness for use or suitability for any purpose, express 146> or implied. Use at your own risk or not at all. 147> =================================================================== 148> 149> Incorporating the code into commercial products is permitted; you do 150> not have to make source available or contribute your changes back 151> (though that would be nice). 152> 153> --amk (www.amk.ca) 154> 155> For the next PyCrypto release, I would like to take steps to move toward a 156> clearer licensing regime. I am asking as many copyright holders as I can 157> find if I can release PyCrypto under something clearer and more standard. 158> Below, I have quoted a public domain dedication that was recommended in 159> _Intellectual Property and Open Source: A Practical Guide to Protecting 160> Code_, by Van Lindberg. I have already contacted A. M. Kuchling, Robey 161> Pointer, and Wim Lewis, and they have all approved the following text for 162> their contributions. 163> 164> I understand that you have made contributions to PyCrypto. May I, on your 165> behalf, dedicate to the public domain all your contributions to PyCrypto, 166> with the following notice? 167> 168> ======================================================================= 169> The contents of this file are dedicated to the public domain. To the 170> extent that dedication to the public domain is not available, everyone 171> is granted a worldwide, perpetual, royalty-free, non-exclusive license 172> to exercise all rights associated with the contents of this file for 173> any purpose whatsoever. No rights are reserved. 174> ======================================================================= 175> 176> Regards, 177> - Dwayne 178> 179> -- 180> Dwayne C. Litzenberger <dlitz@dlitz.net> 181> Key-signing key - 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7 182> 183 184 185 186-- 187Jeethu Rao 188 189--000e0cd209d0e5a3d40464a23054 190Content-Type: text/html; charset=ISO-8859-1 191Content-Transfer-Encoding: quoted-printable 192 193Hi Dwayne,<div>My contribution to pycrypto are very very minimal (The sha25= 1946 module, IIRC).</div><div>I'd be fine with the public domain license f= 195or PyCrypto.</div><div><br></div><div>Jeethu Rao</div><div>PS: Apologies fo= 196r the delay in my response.=A0</div> 197<div>I don't really check this email address all that often,</div><div>= 198please direct any further correspondence to <a href=3D"mailto:jeethu@jeethu= 199rao.com">jeethu@jeethurao.com</a><br><div><br><div class=3D"gmail_quote">On= 200 Sun, Mar 1, 2009 at 9:54 AM, Dwayne C. Litzenberger <span dir=3D"ltr"><= 201<a href=3D"mailto:dlitz@dlitz.net">dlitz@dlitz.net</a>></span> wrote:<br= 202> 203<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= 204x #ccc solid;padding-left:1ex;">Hi Jeethu,<br> 205<br> 206I am the new maintainer of the Python Cryptography Toolkit, and I am workin= 207g on a new release at <a href=3D"http://www.pycrypto.org/" target=3D"_blank= 208">http://www.pycrypto.org/</a>.<br> 209<br> 210People often ask me what license PyCrypto is covered by, if it's GPL-co= 211mpatible, etc. =A0Right now, I'm not really sure what to tell them. =A0= 212The text in the current LICENSE file (quoted below) is not entirely clear o= 213n the point of whether distributing modified versions is allowed. =A0(It sa= 214ys "distribute and use", but not "modify".)<br> 215 216<br> 217=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 218=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 219=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> 220Distribute and use freely; there are no restrictions on further<br> 221dissemination and usage except those imposed by the laws of your<br> 222country of residence. =A0This software is provided "as is" withou= 223t<br> 224warranty of fitness for use or suitability for any purpose, express<br> 225or implied. Use at your own risk or not at all.<br> 226=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 227=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 228=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> 229<br> 230Incorporating the code into commercial products is permitted; you do<br> 231not have to make source available or contribute your changes back<br> 232(though that would be nice).<br> 233<br> 234--amk =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = 235=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(<a href=3D"http://www.amk.ca" target=3D= 236"_blank">www.amk.ca</a>)<br> 237<br> 238For the next PyCrypto release, I would like to take steps to move toward a = 239clearer licensing regime. =A0I am asking as many copyright holders as I can= 240 find if I can release PyCrypto under something clearer and more standard. = 241=A0Below, I have quoted a public domain dedication that was recommended in = 242_Intellectual Property and Open Source: A Practical Guide to Protecting Cod= 243e_, by Van Lindberg. =A0I have already contacted A. M. Kuchling, Robey Poin= 244ter, and Wim Lewis, and they have all approved the following text for their= 245 contributions.<br> 246 247<br> 248I understand that you have made contributions to PyCrypto. =A0May I, on you= 249r behalf, dedicate to the public domain all your contributions to PyCrypto,= 250 with the following notice?<br> 251<br> 252=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 253=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 254=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> 255The contents of this file are dedicated to the public domain. =A0To the<br> 256extent that dedication to the public domain is not available, everyone<br> 257is granted a worldwide, perpetual, royalty-free, non-exclusive license<br> 258to exercise all rights associated with the contents of this file for<br> 259any purpose whatsoever. =A0No rights are reserved.<br> 260=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 261=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= 262=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<br> 263<br> 264Regards,<br> 265- Dwayne<br><font color=3D"#888888"> 266<br> 267-- <br> 268Dwayne C. Litzenberger <<a href=3D"mailto:dlitz@dlitz.net" target=3D"_bl= 269ank">dlitz@dlitz.net</a>><br> 270 =A0 =A0 =A0Key-signing key =A0 - 19E1 1FE8 B3CF F273 ED17 =A04A24 928C EC1= 2713 39C2 5CF7<br> 272</font></blockquote></div><br><br clear=3D"all"><br>-- <br>Jeethu Rao<br> 273</div></div> 274 275--000e0cd209d0e5a3d40464a23054-- 276 277 278