Gestionnaire de fichiers - Editer - /usr/share/licenses/python-crypto/LEGAL/copy/stmts/Andrew_M_Kuchling.mbox
Arrière
From dlitz@dlitz.net Sun Nov 23 00:17:22 2008 Date: Sun, 23 Nov 2008 00:17:22 -0500 From: "Dwayne C. Litzenberger" <dlitz@dlitz.net> To: "A. M. Kuchling" <amk@amk.ca> Subject: PyCrypto license clarification Message-ID: <20081123051722.GA29253@rivest.dlitz.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline X-Primary-Address: dlitz@dlitz.net X-Homepage: http://www.dlitz.net/ X-OpenPGP: url=http://www.dlitz.net/go/gpgkey/; id=19E11FE8B3CFF273ED174A24928CEC1339C25CF7 (only for key signing); preference=unprotected X-OpenPGP: url=http://www.dlitz.net/go/gpgkey/; id=4B2AFD82FC7D9E3838D9179F1C11B877E7804B45 (2008); preference=signencrypt User-Agent: Mutt/1.5.16 (2007-06-11) Status: RO Content-Length: 3461 Lines: 78 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Andrew, People often ask me what license PyCrypto is covered by, if it's=20 GPL-compatible, etc. Right now, I'm not really sure what to tell them. =20 The text in the current LICENSE file (quoted below) is not entirely clear= =20 on the point of whether distributing modified versions is allowed. (It=20 says "distribute and use", but not "modify".) =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Distribute and use freely; there are no restrictions on further dissemination and usage except those imposed by the laws of your country of residence. This software is provided "as is" without warranty of fitness for use or suitability for any purpose, express or implied. Use at your own risk or not at all. =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Incorporating the code into commercial products is permitted; you do not have to make source available or contribute your changes back (though that would be nice). --amk (www.amk.ca) For the next PyCrypto release, I'd like to take steps to move toward a=20 clearer licensing regime. I'm asking as many copyright holders as I can=20 find, starting with you, if I can release PyCrypto under something clearer= =20 and more standard. Below, I have quoted a public domain dedication that=20 was recommended in _Intellectual Property and Open Source: A Practical=20 Guide to Protecting Code_, by Van Lindberg. May I, on your behalf, dedicate to the public domain your considerable=20 contributions to PyCrypto, with the following notice? =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D The contents of this file are dedicated to the public domain. To the extent that dedication to the public domain is not available, everyone is granted a worldwide, perpetual, royalty-free, non-exclusive license to exercise all rights associated with the contents of this file for any purpose whatsoever. No rights are reserved. =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=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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Regards, - Dwayne --=20 Dwayne C. Litzenberger <dlitz@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 --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iEYEARECAAYFAkko52IACgkQHBG4d+eAS0XPPQCfcyQ2DdAXKg9N7Z+jeSFFD5EZ yloAn33a3ZjkteyJaTbzEqImOEW8JGpf =aBEW -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- From amk@amk.ca Sun Nov 23 07:51:59 2008 X-Maildir-Dup-Checked: Yes Return-Path: <amk@amk.ca> X-Original-To: dwon@rivest.dlitz.net Delivered-To: dwon@rivest.dlitz.net Received: from goedel.dlitz.net (unknown [10.159.255.6]) by rivest.dlitz.net (Postfix) with ESMTP id 5C2C75047D for <dwon@rivest.dlitz.net>; Sun, 23 Nov 2008 07:51:59 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by goedel.dlitz.net (Postfix) with QMQP id D632D10111 for <dwon@rivest.dlitz.net>; Sun, 23 Nov 2008 06:51:58 -0600 (CST) Received: (vmailmgr-postfix 12026 invoked by uid 1003); 23 Nov 2008 06:51:58 -0600 Delivered-To: m-dlitz-dlitz@dlitz.net Received-SPF: none (goedel.dlitz.net: domain of amk@amk.ca does not designate permitted sender hosts) Received: from mail5.sea5.speakeasy.net (mail5.sea5.speakeasy.net [69.17.117.7]) by goedel.dlitz.net (Postfix) with ESMTP id 97DC710105 for <dlitz@dlitz.net>; Sun, 23 Nov 2008 06:51:58 -0600 (CST) Received: (qmail 3992 invoked from network); 23 Nov 2008 12:51:52 -0000 Received: from dsl092-163-165.wdc2.dsl.speakeasy.net (HELO localhost) (akuchling@[66.92.163.165]) (envelope-sender <amk@amk.ca>) by mail5.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for <dlitz@dlitz.net>; 23 Nov 2008 12:51:52 -0000 Date: Sun, 23 Nov 2008 07:51:34 -0500 From: "A.M. Kuchling" <amk@amk.ca> To: "Dwayne C. Litzenberger" <dlitz@dlitz.net> Subject: Re: PyCrypto license clarification Message-ID: <20081123125134.GA21239@amk.local> Reply-To: amk@amk.ca References: <20081123051722.GA29253@rivest.dlitz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081123051722.GA29253@rivest.dlitz.net> User-Agent: Mutt/1.5.13 (2006-08-11) Status: RO Content-Length: 537 Lines: 15 > People often ask me what license PyCrypto is covered by, if it's > GPL-compatible, etc. Right now, I'm not really sure what to tell them. > The text in the current LICENSE file (quoted below) is not entirely clear > on the point of whether distributing modified versions is allowed. (It > says "distribute and use", but not "modify".) The intention is that it be public domain. > May I, on your behalf, dedicate to the public domain your considerable > contributions to PyCrypto, with the following notice? You may. --amk
| ver. 1.4 |
Github
|
.
| PHP 8.0.30 | Génération de la page: 0 |
proxy
|
phpinfo
|
Réglages