Gestionnaire de fichiers - Editer - /usr/share/licenses/python-crypto/LEGAL/copy/stmts/Barry_A_Warsaw.mbox
Arrière
From dlitz@dlitz.net Sat Feb 28 21:45:09 2009 Date: Sat, 28 Feb 2009 21:45:09 -0500 From: "Dwayne C. Litzenberger" <dlitz@dlitz.net> To: Barry A Warsaw <barry@python.org> Subject: PyCrypto license clarification Message-ID: <20090301024509.GA13195@rivest.dlitz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.5.16 (2007-06-11) Status: RO Content-Length: 2535 Hi Barry, I am the new maintainer of the Python Cryptography Toolkit, and I am working on a new release at http://www.pycrypto.org/. 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".) =================================================================== 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. =================================================================== 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 would like to take steps to move toward a clearer licensing regime. I am asking as many copyright holders as I can find if I can release PyCrypto under something clearer and more standard. Below, I have quoted a public domain dedication that was recommended in _Intellectual Property and Open Source: A Practical Guide to Protecting Code_, by Van Lindberg. I have already contacted A. M. Kuchling, Robey Pointer, and Wim Lewis, and they have all approved the following dedication for their contributions. I understand that you have made contributions to PyCrypto. May I, on your behalf, dedicate to the public domain all your contributions to PyCrypto, with the following notice? ======================================================================= 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. ======================================================================= Regards, - Dwayne -- Dwayne C. Litzenberger <dlitz@dlitz.net> Key-signing key - 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7 From barry@python.org Mon Mar 2 11:29:39 2009 X-Maildir-Dup-Checked: Yes Return-Path: <barry@python.org> 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 6E01AC6640B for <dwon@rivest.dlitz.net>; Mon, 2 Mar 2009 11:29:39 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by goedel.dlitz.net (Postfix) with QMQP id 0644E1007A for <dwon@rivest.dlitz.net>; Mon, 2 Mar 2009 10:29:39 -0600 (CST) Received: (vmailmgr-postfix 8668 invoked by uid 1003); 2 Mar 2009 10:29:39 -0600 Delivered-To: m-dlitz-dlitz@dlitz.net Received-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 Received: from mail.wooz.org (216-15-33-230.c3-0.slvr-ubr2.lnh-slvr.md.static.cable.rcn.com [216.15.33.230]) by goedel.dlitz.net (Postfix) with ESMTP id CCEA110073 for <dlitz@dlitz.net>; Mon, 2 Mar 2009 10:29:38 -0600 (CST) Received: from snowdog.wooz.org (snowdog.wooz.org [192.168.11.202]) by mail.wooz.org (Postfix) with ESMTPSA id ACE30E3C9F for <dlitz@dlitz.net>; Mon, 2 Mar 2009 11:29:35 -0500 (EST) Message-Id: <09BF1A39-B015-4820-97A3-8642490C8254@python.org> From: Barry Warsaw <barry@python.org> To: Dwayne C. Litzenberger <dlitz@dlitz.net> In-Reply-To: <20090301024509.GA13195@rivest.dlitz.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: PyCrypto license clarification Date: Mon, 2 Mar 2009 11:29:34 -0500 References: <20090301024509.GA13195@rivest.dlitz.net> X-Pgp-Agent: GPGMail d55 (v55, Leopard) X-Mailer: Apple Mail (2.930.3) Status: RO Content-Length: 869 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Feb 28, 2009, at 9:45 PM, Dwayne C. Litzenberger wrote: > I am the new maintainer of the Python Cryptography Toolkit, and I am =20= > working on a new release at http://www.pycrypto.org/. Great! I'm glad to see someone taking up the mantle of this important =20= Python library. > I understand that you have made contributions to PyCrypto. May I, =20 > on your behalf, dedicate to the public domain all your contributions =20= > to PyCrypto, with the following notice? Absolutely yes. Cheers, Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSawJbnEjvBPtnXfVAQLZjgP/ecG+JdZwNvPJRfsa6rhY6+MHLDHI6agk evkJnSJQAcVHlZnVlVeR5IXgvDUMakZjU4SOV7MqkhsKA9lIet7PaD9VSYgn3ra5 gElwI2DQDoOy5GExXMm74gqrrb1PCCbCRmpaYNo+DZohwHkeFBjbwDRA3wItOrH7 SK4w9VBJtfY=3D =3DQduY -----END PGP SIGNATURE-----
| ver. 1.4 |
Github
|
.
| PHP 8.0.30 | Génération de la page: 0 |
proxy
|
phpinfo
|
Réglages