Git-Mirrors/sec-pentesting-toolkit
1
0
Fork 0
mirror of https://github.com/autistic-symposium/sec-pentesting-toolkit.git synced 2025-08-02 19:56:14 -04:00
Code Issues Projects Releases Packages Wiki Activity

some small fixes

Browse source
This commit is contained in:
Mari Wahl 2014-10-11 01:54:02 -04:00
parent 52067188ed
commit 9cdfa95054
89 changed files with 27401 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

4
Cryptography/pycrypto-2.6.1/LEGAL/copy/00INDEX Normal file
View file

@ -0,0 +1,4 @@
00INDEX This file
LICENSE.orig Original (deprecated) license for the Python Cryptography Toolkit
LICENSE.libtom LICENSE file from LibTomCrypt
stmts/ Statements by contributors

5
Cryptography/pycrypto-2.6.1/LEGAL/copy/LICENSE.libtom Normal file
View file

@ -0,0 +1,5 @@
LibTomCrypt is public domain. As should all quality software be.
Tom St Denis

15
Cryptography/pycrypto-2.6.1/LEGAL/copy/LICENSE.orig Normal file
View file

@ -0,0 +1,15 @@
===================================================================
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)

253
Cryptography/pycrypto-2.6.1/LEGAL/copy/LICENSE.python-2.2 Normal file
View file

@ -0,0 +1,253 @@
A. HISTORY OF THE SOFTWARE
==========================
Python was created in the early 1990s by Guido van Rossum at Stichting
Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands
as a successor of a language called ABC. Guido remains Python's
principal author, although it includes many contributions from others.
In 1995, Guido continued his work on Python at the Corporation for
National Research Initiatives (CNRI, see http://www.cnri.reston.va.us)
in Reston, Virginia where he released several versions of the
software.
In May 2000, Guido and the Python core development team moved to
BeOpen.com to form the BeOpen PythonLabs team. In October of the same
year, the PythonLabs team moved to Digital Creations (now Zope
Corporation, see http://www.zope.com). In 2001, the Python Software
Foundation (PSF, see http://www.python.org/psf/) was formed, a
non-profit organization created specifically to own Python-related
Intellectual Property. Zope Corporation is a sponsoring member of
the PSF.
All Python releases are Open Source (see http://www.opensource.org for
the Open Source Definition). Historically, most, but not all, Python
releases have also been GPL-compatible; the table below summarizes
the various releases.
Release Derived Year Owner GPL-
from compatible? (1)
0.9.0 thru 1.2 1991-1995 CWI yes
1.3 thru 1.5.2 1.2 1995-1999 CNRI yes
1.6 1.5.2 2000 CNRI no
2.0 1.6 2000 BeOpen.com no
1.6.1 1.6 2001 CNRI no
2.1 2.0+1.6.1 2001 PSF no
2.0.1 2.0+1.6.1 2001 PSF yes
2.1.1 2.1+2.0.1 2001 PSF yes
2.2 2.1.1 2001 PSF yes
2.1.2 2.1.1 2002 PSF yes
2.1.3 2.1.2 2002 PSF yes
2.2.1 2.2 2002 PSF yes
2.2.2 2.2.1 2002 PSF yes
2.2.3 2.2.2 2003 PSF yes
Footnotes:
(1) GPL-compatible doesn't mean that we're distributing Python under
the GPL. All Python licenses, unlike the GPL, let you distribute
a modified version without making your changes open source. The
GPL-compatible licenses make it possible to combine Python with
other software that is released under the GPL; the others don't.
Thanks to the many outside volunteers who have worked under Guido's
direction to make these releases possible.
B. TERMS AND CONDITIONS FOR ACCESSING OR OTHERWISE USING PYTHON
===============================================================
PSF LICENSE AGREEMENT FOR PYTHON 2.2.3
--------------------------------------
1. This LICENSE AGREEMENT is between the Python Software Foundation
("PSF"), and the Individual or Organization ("Licensee") accessing and
otherwise using Python 2.2.3 software in source or binary form and its
associated documentation.
2. Subject to the terms and conditions of this License Agreement, PSF
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python 2.2.3
alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright, i.e., "Copyright (c)
2001, 2002, 2003 Python Software Foundation; All Rights Reserved" are
retained in Python 2.2.3 alone or in any derivative version prepared
by Licensee.
3. In the event Licensee prepares a derivative work that is based on
or incorporates Python 2.2.3 or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python 2.2.3.
4. PSF is making Python 2.2.3 available to Licensee on an "AS IS"
basis. PSF MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, PSF MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 2.2.3 WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
5. PSF SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
2.2.3 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 2.2.3,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
7. Nothing in this License Agreement shall be deemed to create any
relationship of agency, partnership, or joint venture between PSF and
Licensee. This License Agreement does not grant permission to use PSF
trademarks or trade name in a trademark sense to endorse or promote
products or services of Licensee, or any third party.
8. By copying, installing or otherwise using Python 2.2.3, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.
BEOPEN.COM LICENSE AGREEMENT FOR PYTHON 2.0
-------------------------------------------
BEOPEN PYTHON OPEN SOURCE LICENSE AGREEMENT VERSION 1
1. This LICENSE AGREEMENT is between BeOpen.com ("BeOpen"), having an
office at 160 Saratoga Avenue, Santa Clara, CA 95051, and the
Individual or Organization ("Licensee") accessing and otherwise using
this software in source or binary form and its associated
documentation ("the Software").
2. Subject to the terms and conditions of this BeOpen Python License
Agreement, BeOpen hereby grants Licensee a non-exclusive,
royalty-free, world-wide license to reproduce, analyze, test, perform
and/or display publicly, prepare derivative works, distribute, and
otherwise use the Software alone or in any derivative version,
provided, however, that the BeOpen Python License is retained in the
Software, alone or in any derivative version prepared by Licensee.
3. BeOpen is making the Software available to Licensee on an "AS IS"
basis. BEOPEN MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, BEOPEN MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE SOFTWARE WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
4. BEOPEN SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF THE
SOFTWARE FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS
AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THE SOFTWARE, OR ANY
DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
5. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
6. This License Agreement shall be governed by and interpreted in all
respects by the law of the State of California, excluding conflict of
law provisions. Nothing in this License Agreement shall be deemed to
create any relationship of agency, partnership, or joint venture
between BeOpen and Licensee. This License Agreement does not grant
permission to use BeOpen trademarks or trade names in a trademark
sense to endorse or promote products or services of Licensee, or any
third party. As an exception, the "BeOpen Python" logos available at
http://www.pythonlabs.com/logos.html may be used according to the
permissions granted on that web page.
7. By copying, installing or otherwise using the software, Licensee
agrees to be bound by the terms and conditions of this License
Agreement.
CNRI LICENSE AGREEMENT FOR PYTHON 1.6.1
---------------------------------------
1. This LICENSE AGREEMENT is between the Corporation for National
Research Initiatives, having an office at 1895 Preston White Drive,
Reston, VA 20191 ("CNRI"), and the Individual or Organization
("Licensee") accessing and otherwise using Python 1.6.1 software in
source or binary form and its associated documentation.
2. Subject to the terms and conditions of this License Agreement, CNRI
hereby grants Licensee a nonexclusive, royalty-free, world-wide
license to reproduce, analyze, test, perform and/or display publicly,
prepare derivative works, distribute, and otherwise use Python 1.6.1
alone or in any derivative version, provided, however, that CNRI's
License Agreement and CNRI's notice of copyright, i.e., "Copyright (c)
1995-2001 Corporation for National Research Initiatives; All Rights
Reserved" are retained in Python 1.6.1 alone or in any derivative
version prepared by Licensee. Alternately, in lieu of CNRI's License
Agreement, Licensee may substitute the following text (omitting the
quotes): "Python 1.6.1 is made available subject to the terms and
conditions in CNRI's License Agreement. This Agreement together with
Python 1.6.1 may be located on the Internet using the following
unique, persistent identifier (known as a handle): 1895.22/1013. This
Agreement may also be obtained from a proxy server on the Internet
using the following URL: http://hdl.handle.net/1895.22/1013".
3. In the event Licensee prepares a derivative work that is based on
or incorporates Python 1.6.1 or any part thereof, and wants to make
the derivative work available to others as provided herein, then
Licensee hereby agrees to include in any such work a brief summary of
the changes made to Python 1.6.1.
4. CNRI is making Python 1.6.1 available to Licensee on an "AS IS"
basis. CNRI MAKES NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR
IMPLIED. BY WAY OF EXAMPLE, BUT NOT LIMITATION, CNRI MAKES NO AND
DISCLAIMS ANY REPRESENTATION OR WARRANTY OF MERCHANTABILITY OR FITNESS
FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF PYTHON 1.6.1 WILL NOT
INFRINGE ANY THIRD PARTY RIGHTS.
5. CNRI SHALL NOT BE LIABLE TO LICENSEE OR ANY OTHER USERS OF PYTHON
1.6.1 FOR ANY INCIDENTAL, SPECIAL, OR CONSEQUENTIAL DAMAGES OR LOSS AS
A RESULT OF MODIFYING, DISTRIBUTING, OR OTHERWISE USING PYTHON 1.6.1,
OR ANY DERIVATIVE THEREOF, EVEN IF ADVISED OF THE POSSIBILITY THEREOF.
6. This License Agreement will automatically terminate upon a material
breach of its terms and conditions.
7. This License Agreement shall be governed by the federal
intellectual property law of the United States, including without
limitation the federal copyright law, and, to the extent such
U.S. federal law does not apply, by the law of the Commonwealth of
Virginia, excluding Virginia's conflict of law provisions.
Notwithstanding the foregoing, with regard to derivative works based
on Python 1.6.1 that incorporate non-separable material that was
previously distributed under the GNU General Public License (GPL), the
law of the Commonwealth of Virginia shall govern this License
Agreement only as to issues arising under or with respect to
Paragraphs 4, 5, and 7 of this License Agreement. Nothing in this
License Agreement shall be deemed to create any relationship of
agency, partnership, or joint venture between CNRI and Licensee. This
License Agreement does not grant permission to use CNRI trademarks or
trade name in a trademark sense to endorse or promote products or
services of Licensee, or any third party.
8. By clicking on the "ACCEPT" button where indicated, or by copying,
installing or otherwise using Python 1.6.1, Licensee agrees to be
bound by the terms and conditions of this License Agreement.
ACCEPT
CWI LICENSE AGREEMENT FOR PYTHON 0.9.0 THROUGH 1.2
--------------------------------------------------
Copyright (c) 1991 - 1995, Stichting Mathematisch Centrum Amsterdam,
The Netherlands. All rights reserved.
Permission to use, copy, modify, and distribute this software and its
documentation for any purpose and without fee is hereby granted,
provided that the above copyright notice appear in all copies and that
both that copyright notice and this permission notice appear in
supporting documentation, and that the name of Stichting Mathematisch
Centrum or CWI not be used in advertising or publicity pertaining to
distribution of the software without specific, written prior
permission.
STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE
FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

156
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Andrew_M_Kuchling.mbox Normal file
View file

@ -0,0 +1,156 @@
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

135
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Barry_A_Warsaw.mbox Normal file
View file

@ -0,0 +1,135 @@
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-----

277
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Jeethu_Rao.mbox Normal file
View file

@ -0,0 +1,277 @@
From dlitz@dlitz.net Sat Feb 28 23:24:14 2009
Date: Sat, 28 Feb 2009 23:24:14 -0500
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: Jeethu Rao <jeethurao@gmail.com>
Subject: PyCrypto license clarification
Message-ID: <20090301042414.GA15122@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: 2513
Hi Jeethu,
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 text 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 jeethurao@gmail.com Sun Mar 8 17:28:16 2009
X-Maildir-Dup-Checked: Yes
Return-Path: <jeethurao@gmail.com>
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 0CC83515D9
for <dwon@rivest.dlitz.net>; Sun, 8 Mar 2009 17:28:16 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
by goedel.dlitz.net (Postfix) with QMQP id 4E58F450CB
for <dwon@rivest.dlitz.net>; Sun, 8 Mar 2009 15:28:15 -0600 (CST)
Received: (vmailmgr-postfix 5011 invoked by uid 1003); 8 Mar 2009 15:28:15 -0600
Delivered-To: m-dlitz-dlitz@dlitz.net
Received-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
Received: from rv-out-0708.google.com (unknown [209.85.198.249])
by goedel.dlitz.net (Postfix) with ESMTP id 3C097449E7
for <dlitz@dlitz.net>; Sun, 8 Mar 2009 15:28:12 -0600 (CST)
Received: by rv-out-0708.google.com with SMTP id k29so1252333rvb.26
for <dlitz@dlitz.net>; Sun, 08 Mar 2009 14:27:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:date:message-id:subject:from:to:content-type;
bh=YWy9U32WCU/ksRqukHwaOZyJQBUs4Yvt5mI20U6mI/g=;
b=oMjI22lIxYiJKge2zNJW3rRiUi9LqFXmey5Wp0pLItuNF+X3duyfhopTuBAKw7MwVY
B5E6VQuGVEyzBbNsctyVgq6DhQiQtouCLZymSViobmuDmKn5DtUKoxpDk0xCxQmHYaas
L9/A6D3/J66kKrNBgX9mc0GPcZTviVFYkPR0Q=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=Ym7CStuDEfJKay1AJyWZkZmJA1lnTcwCG6akBHAXLld8ht6PFcmlsffzZG8hJCIVJ8
vljqcT+G6cywVTBw1pyGX7ECYzr0+vhGvgdpACGrs24zikHfpSSd5GFogzXaLVvGVH8p
bqSHpfWKKtEP4gAQkiNeIq1GNtR2j8U3fnRyg=
MIME-Version: 1.0
Received: by 10.141.176.13 with SMTP id d13mr2656028rvp.231.1236547674677;
Sun, 08 Mar 2009 14:27:54 -0700 (PDT)
In-Reply-To: <20090301042414.GA15122@rivest.dlitz.net>
References: <20090301042414.GA15122@rivest.dlitz.net>
Date: Mon, 9 Mar 2009 02:57:54 +0530
Message-ID: <e3c0ddba0903081427p3a7b1058g417dd8624df68d6d@mail.gmail.com>
Subject: Re: PyCrypto license clarification
From: Jeethu Rao <jeethurao@gmail.com>
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
Content-Type: multipart/alternative; boundary=000e0cd209d0e5a3d40464a23054
Status: RO
Content-Length: 7668
--000e0cd209d0e5a3d40464a23054
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Hi Dwayne,My contribution to pycrypto are very very minimal (The sha256
module, IIRC).
I'd be fine with the public domain license for PyCrypto.
Jeethu Rao
PS: Apologies for the delay in my response.
I don't really check this email address all that often,
please direct any further correspondence to jeethu@jeethurao.com
On Sun, Mar 1, 2009 at 9:54 AM, Dwayne C. Litzenberger <dlitz@dlitz.net>wrote:
> Hi Jeethu,
>
> 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 text 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
>
--
Jeethu Rao
--000e0cd209d0e5a3d40464a23054
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi Dwayne,<div>My contribution to pycrypto are very very minimal (The sha25=
6 module, IIRC).</div><div>I&#39;d be fine with the public domain license f=
or PyCrypto.</div><div><br></div><div>Jeethu Rao</div><div>PS: Apologies fo=
r the delay in my response.=A0</div>
<div>I don&#39;t really check this email address all that often,</div><div>=
please direct any further correspondence to <a href=3D"mailto:jeethu@jeethu=
rao.com">jeethu@jeethurao.com</a><br><div><br><div class=3D"gmail_quote">On=
Sun, Mar 1, 2009 at 9:54 AM, Dwayne C. Litzenberger <span dir=3D"ltr">&lt;=
<a href=3D"mailto:dlitz@dlitz.net">dlitz@dlitz.net</a>&gt;</span> wrote:<br=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Hi Jeethu,<br>
<br>
I am the new maintainer of the Python Cryptography Toolkit, and I am workin=
g on a new release at <a href=3D"http://www.pycrypto.org/" target=3D"_blank=
">http://www.pycrypto.org/</a>.<br>
<br>
People often ask me what license PyCrypto is covered by, if it&#39;s GPL-co=
mpatible, etc. =A0Right now, I&#39;m not really sure what to tell them. =A0=
The text in the current LICENSE file (quoted below) is not entirely clear o=
n the point of whether distributing modified versions is allowed. =A0(It sa=
ys &quot;distribute and use&quot;, but not &quot;modify&quot;.)<br>
<br>
=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<br>
Distribute and use freely; there are no restrictions on further<br>
dissemination and usage except those imposed by the laws of your<br>
country of residence. =A0This software is provided &quot;as is&quot; withou=
t<br>
warranty of fitness for use or suitability for any purpose, express<br>
or implied. Use at your own risk or not at all.<br>
=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<br>
<br>
Incorporating the code into commercial products is permitted; you do<br>
not have to make source available or contribute your changes back<br>
(though that would be nice).<br>
<br>
--amk =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(<a href=3D"http://www.amk.ca" target=3D=
"_blank">www.amk.ca</a>)<br>
<br>
For the next PyCrypto release, I would like to take steps to move toward a =
clearer licensing regime. =A0I am asking as many copyright holders as I can=
find if I can release PyCrypto under something clearer and more standard. =
=A0Below, I have quoted a public domain dedication that was recommended in =
_Intellectual Property and Open Source: A Practical Guide to Protecting Cod=
e_, by Van Lindberg. =A0I have already contacted A. M. Kuchling, Robey Poin=
ter, and Wim Lewis, and they have all approved the following text for their=
contributions.<br>
<br>
I understand that you have made contributions to PyCrypto. =A0May I, on you=
r behalf, dedicate to the public domain all your contributions to PyCrypto,=
with the following notice?<br>
<br>
=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<br>
The contents of this file are dedicated to the public domain. =A0To the<br>
extent that dedication to the public domain is not available, everyone<br>
is granted a worldwide, perpetual, royalty-free, non-exclusive license<br>
to exercise all rights associated with the contents of this file for<br>
any purpose whatsoever. =A0No rights are reserved.<br>
=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<br>
<br>
Regards,<br>
- Dwayne<br><font color=3D"#888888">
<br>
-- <br>
Dwayne C. Litzenberger &lt;<a href=3D"mailto:dlitz@dlitz.net" target=3D"_bl=
ank">dlitz@dlitz.net</a>&gt;<br>
=A0 =A0 =A0Key-signing key =A0 - 19E1 1FE8 B3CF F273 ED17 =A04A24 928C EC1=
3 39C2 5CF7<br>
</font></blockquote></div><br><br clear=3D"all"><br>-- <br>Jeethu Rao<br>
</div></div>
--000e0cd209d0e5a3d40464a23054--

298
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Joris_Bontje.mbox Normal file
View file

@ -0,0 +1,298 @@
From dlitz@dlitz.net Mon May 4 22:49:14 2009
Date: Mon, 4 May 2009 22:49:14 -0400
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: Joris Bontje <joris@bontje.nl>
Subject: PyCrypto license clarification
Message-ID: <20090505024914.GA9219@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: 2553
Hi Joris,
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, Barry Warsaw, Wim Lewis, Jeethu Rao, and Mark Moraes, 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 joris@bontje.nl Tue May 5 03:08:32 2009
X-Maildir-Dup-Checked: Yes
Return-Path: <joris@bontje.nl>
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 7AA4B9E5078
for <dwon@rivest.dlitz.net>; Tue, 5 May 2009 03:08:32 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
by goedel.dlitz.net (Postfix) with QMQP id 2315B40583
for <dwon@rivest.dlitz.net>; Tue, 5 May 2009 01:08:32 -0600 (CST)
Received: (vmailmgr-postfix 16890 invoked by uid 1003); 5 May 2009 01:08:32 -0600
Delivered-To: m-dlitz-dlitz@dlitz.net
Received-SPF: none (bontje.nl: No applicable sender policy available) receiver=goedel.dlitz.net; identity=mfrom; envelope-from="joris@bontje.nl"; helo=smtp6.versatel.nl; client-ip=62.58.50.97
Received: from smtp6.versatel.nl (smtp6.versatel.nl [62.58.50.97])
by goedel.dlitz.net (Postfix) with ESMTP id 2D76A4052C
for <dlitz@dlitz.net>; Tue, 5 May 2009 01:08:30 -0600 (CST)
Received: (qmail 4224 invoked by uid 0); 5 May 2009 07:08:25 -0000
Received: from qmail06.zonnet.nl (HELO dell062.admin.zonnet.nl) ([10.170.1.123])
(envelope-sender <joris@bontje.nl>)
by 10.170.1.96 (qmail-ldap-1.03) with SMTP
for < >; 5 May 2009 07:08:25 -0000
Received: by dell062.admin.zonnet.nl (Postfix, from userid 33)
id 9BE9B15759B; Tue, 5 May 2009 09:08:25 +0200 (CEST)
Received: from firewall66.interaccess.nl (firewall66.interaccess.nl
[193.173.35.66]) by www.webmail.vuurwerk.nl (Horde MIME library) with HTTP;
Tue, 05 May 2009 09:08:25 +0200
Message-ID: <20090505090825.gsq1ps7hg08wwwok@www.webmail.vuurwerk.nl>
Date: Tue, 05 May 2009 09:08:25 +0200
From: joris@bontje.nl
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
Subject: Re: PyCrypto license clarification
References: <20090505024914.GA9219@rivest.dlitz.net>
In-Reply-To: <20090505024914.GA9219@rivest.dlitz.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset=ISO-8859-1;
format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.3)
Status: RO
X-Status: A
Content-Length: 3488
Hi Dwayne,
Thanks for taking over the PyCrypto library and putting in the required
effort to keep this going.
I was very excited to read that it is now one of the installed
libraries for Google AppsEngine!
You have my full permission to dedicate all my contributions to
PyCrypto to the public domain with your suggested 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,
Joris
Citeren "Dwayne C. Litzenberger" <dlitz@dlitz.net>:
> Hi Joris,
>
> 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, Barry Warsaw, Wim Lewis, Jeethu Rao, and Mark Moraes, 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 dlitz@dlitz.net Tue May 5 17:53:47 2009
Date: Tue, 5 May 2009 17:53:47 -0400
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: joris@bontje.nl
Subject: Re: PyCrypto license clarification
Message-ID: <20090505215347.GB9933@rivest.dlitz.net>
References: <20090505024914.GA9219@rivest.dlitz.net> <20090505090825.gsq1ps7hg08wwwok@www.webmail.vuurwerk.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <20090505090825.gsq1ps7hg08wwwok@www.webmail.vuurwerk.nl>
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: 3863
Excellent! Thank you!
On Tue, May 05, 2009 at 09:08:25AM +0200, joris@bontje.nl wrote:
> Hi Dwayne,
>
> Thanks for taking over the PyCrypto library and putting in the required
> effort to keep this going.
> I was very excited to read that it is now one of the installed libraries
> for Google AppsEngine!
>
> You have my full permission to dedicate all my contributions to PyCrypto to
> the public domain with your suggested 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,
> Joris
>
> Citeren "Dwayne C. Litzenberger" <dlitz@dlitz.net>:
>
>> Hi Joris,
>>
>> 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, Barry Warsaw, Wim Lewis, Jeethu Rao, and Mark Moraes, 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
>
>
--
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

340
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Mark_Moraes.mbox Normal file
View file

@ -0,0 +1,340 @@
From dlitz@dlitz.net Sat Apr 18 09:14:20 2009
Date: Sat, 18 Apr 2009 09:14:20 -0400
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: Mark Moraes <moraes@computer.org>
Subject: PyCrypto license clarification
Message-ID: <20090418131419.GA14494@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: 2635
Hi Mark,
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, Wim Lewis, Jeethu Rao, and Barry Warsaw, 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 markmoraes@yahoo.com Mon Apr 20 19:25:37 2009
X-Maildir-Dup-Checked: Yes
Return-Path: <markmoraes@yahoo.com>
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 5D9AE984FDD
for <dwon@rivest.dlitz.net>; Mon, 20 Apr 2009 19:25:37 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
by goedel.dlitz.net (Postfix) with QMQP id DE41F4025F
for <dwon@rivest.dlitz.net>; Mon, 20 Apr 2009 17:25:36 -0600 (CST)
Received: (vmailmgr-postfix 7604 invoked by uid 1003); 20 Apr 2009 17:25:36 -0600
Delivered-To: m-dlitz-dlitz@dlitz.net
Received-SPF: none (yahoo.com: No applicable sender policy available) receiver=goedel.dlitz.net; identity=mfrom; envelope-from="markmoraes@yahoo.com"; helo=web32405.mail.mud.yahoo.com; client-ip=68.142.207.198
Received: from web32405.mail.mud.yahoo.com (web32405.mail.mud.yahoo.com [68.142.207.198])
by goedel.dlitz.net (Postfix) with SMTP id B5EAF401EE
for <dlitz@dlitz.net>; Mon, 20 Apr 2009 17:25:36 -0600 (CST)
Received: (qmail 34697 invoked by uid 60001); 20 Apr 2009 23:25:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1240269933; bh=OvxqbYnCg7R6tUN3YmlgFURM3CuHh1JeHyXhDzkaThU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=F2h2bFzpQxyKFZ8BhenniyupGw4Zvlekb9BSk91qKU+51W/TkSGBij5YZIhkLQdkQk0qLz5f4g8dT6bOME3sEY1j10hlx0K0u2UD0yoYTINBCmsdMQRoJ7ph9bmt+p/EJhRpe+FiV6aoLV0FONWiHfGDghPT1dulWXfVTqgB2aU=
DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws;
s=s1024; d=yahoo.com;
h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
b=r6RShFF5VzQLg+9tcn1xKuo4Rs4IVvXF6fdqOpQrMyRCxeFooebhuTE35grGqlomOJLwM0+mZwRb6rGkDj763caOAlo8Ect/qlADW5izXfmVQaDchTbTqmpsJBmQnTQs9iZ+InrG+3UIwtUSGfX7fhEWmI9P/HBzxf9Wp4b3jeo=;
Message-ID: <551071.34569.qm@web32405.mail.mud.yahoo.com>
X-YMail-OSG: FrK8aWMVM1mFJtLpMGbUbCLjbUQC.i.JkIAKUHSFsFn7t9PbtewAewXJ2uhZGCOlGCX6oVnG3u.CgqzAffY4vZSnfTT8wnCkzZNZ_g6k.XUc3ipo_6e.92TXl4p8MxDGAf1tpNF5nXPwcQ7aREs7jGoWWVJYVytp50clsUFSHzf7Zbpa8P1Yoe_xSzf3OAgRSh5fCrbFCC8sHPCuwrL3YhasbtHmkWffteSS.x6gEcBaxf03oz4FeDb5mpJ54g11Xonq8h_TmzX9g84Bin9g_3fJ4WSXm6g6.tohLyfXcUxoz4j036wyWpTKPrWEzIUQaN83Sv_bj_Ghxw--
Received: from [69.124.140.74] by web32405.mail.mud.yahoo.com via HTTP; Mon, 20 Apr 2009 16:25:32 PDT
X-Mailer: YahooMailClassic/5.2.15 YahooMailWebService/0.7.289.1
Date: Mon, 20 Apr 2009 16:25:32 -0700 (PDT)
From: M Moraes <markmoraes@yahoo.com>
Reply-To: moraes@computer.org
Subject: Re: PyCrypto license clarification
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Status: RO
X-Status: A
Content-Length: 3222
Hi Dwayne.
Sure, the new license sounds fine for all my contributions to PyCrypto, and thanks for taking it on. My apologies for not responding to your previous e-mail.
Regards,
Mark.
--- On Sat, 4/18/09, Dwayne C. Litzenberger <dlitz@dlitz.net> wrote:
> From: Dwayne C. Litzenberger <dlitz@dlitz.net>
> Subject: PyCrypto license clarification
> To: "Mark Moraes" <moraes@computer.org>
> Date: Saturday, April 18, 2009, 9:14 AM
> Hi Mark,
>
> 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, Wim Lewis, Jeethu Rao, and Barry Warsaw, 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 dlitz@dlitz.net Mon Apr 20 20:01:37 2009
Date: Mon, 20 Apr 2009 20:01:37 -0400
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: moraes@computer.org
Subject: Re: PyCrypto license clarification
Message-ID: <20090421000137.GA29012@rivest.dlitz.net>
References: <551071.34569.qm@web32405.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
In-Reply-To: <551071.34569.qm@web32405.mail.mud.yahoo.com>
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: 3677
Thanks a lot, and don't worry about not responding to previous emails. I
do that too much myself. :)
On Mon, Apr 20, 2009 at 04:25:32PM -0700, M Moraes wrote:
>
>Hi Dwayne.
>
>Sure, the new license sounds fine for all my contributions to PyCrypto, and thanks for taking it on. My apologies for not responding to your previous e-mail.
>
>Regards,
>Mark.
>
>--- On Sat, 4/18/09, Dwayne C. Litzenberger <dlitz@dlitz.net> wrote:
>
>> From: Dwayne C. Litzenberger <dlitz@dlitz.net>
>> Subject: PyCrypto license clarification
>> To: "Mark Moraes" <moraes@computer.org>
>> Date: Saturday, April 18, 2009, 9:14 AM
>> Hi Mark,
>>
>> 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, Wim Lewis, Jeethu Rao, and Barry Warsaw, 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
>>
>
--
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

211
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Paul_Swartz.mbox Normal file
View file

@ -0,0 +1,211 @@
From dlitz@dlitz.net Sun Aug 2 21:48:25 2009
Date: Sun, 2 Aug 2009 21:48:25 -0400
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: Paul Swartz <paulswartz@gmail.com>
Subject: PyCrypto license clarification
Message-ID: <20090803014825.GA1326@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: 2631
Hi Paul,
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, Barry Warsaw, Wim Lewis, Jeethu Rao, Joris Bontje, and Mark
Moraes, and they have all approved the following dedication for their
contributions.
I understand that you have made contributions to PyCrypto, under nickname
"z3p" and/or other names. 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 paulswartz@gmail.com Mon Aug 3 12:14:07 2009
X-Maildir-Dup-Checked: Yes
Return-Path: <paulswartz@gmail.com>
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 30B9D984FC4
for <dwon@rivest.dlitz.net>; Mon, 3 Aug 2009 12:14:07 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
by goedel.dlitz.net (Postfix) with QMQP id AD9AE81068
for <dwon@rivest.dlitz.net>; Mon, 3 Aug 2009 10:14:06 -0600 (CST)
Received: (vmailmgr-postfix 32055 invoked by uid 1003); 3 Aug 2009 10:14:06 -0600
Delivered-To: m-dlitz-dlitz@dlitz.net
Received-SPF: pass (gmail.com ... _spf.google.com: 72.14.220.159 is authorized to use 'paulswartz@gmail.com' in 'mfrom' identity (mechanism 'ip4:72.14.192.0/18' matched)) receiver=goedel.dlitz.net; identity=mfrom; envelope-from="paulswartz@gmail.com"; helo=fg-out-1718.google.com; client-ip=72.14.220.159
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159])
by goedel.dlitz.net (Postfix) with ESMTP id 4E63881066
for <dlitz@dlitz.net>; Mon, 3 Aug 2009 10:14:05 -0600 (CST)
Received: by fg-out-1718.google.com with SMTP id d23so1076840fga.3
for <dlitz@dlitz.net>; Mon, 03 Aug 2009 09:14:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:content-type
:content-transfer-encoding;
bh=A0RHBf0TnribKS5qOHJ3WYbkZ+b0cuPeuoKAvpApWcc=;
b=gyTqkRhKlHadFKIZCBWsRbnMNVDq1PWlJbyC0EvxPskaoHr3HAR96MWQNBePu/40Ac
Vn55qlIqTdom4e9zlUEE6MwZo9kqi/Qw0L/SLib0DlQeNqo/eHYqPmuVswltaYwNAyMJ
Y9++76rPGzqYdALsfvsmwv7Q3/bEmjVTr0tQE=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type:content-transfer-encoding;
b=jze7KSMkUGilfVCXKXaaXMi5NAtGdMQOtVZZfRNyGSy68xOd2sxefjyyig3EfT6Nv6
Q3opUMsT96Q6zjZND55w446kTh2uBTNz4d3NwIeEWJnG3xcliRQu/mXPFp8AzPI3CefL
1ornJLM1eQ2XyuZA73jem+SJtfdHUcSD1UhgI=
MIME-Version: 1.0
Received: by 10.239.157.147 with SMTP id q19mr601802hbc.61.1249316043185; Mon,
03 Aug 2009 09:14:03 -0700 (PDT)
In-Reply-To: <20090803014825.GA1326@rivest.dlitz.net>
References: <20090803014825.GA1326@rivest.dlitz.net>
From: Paul Swartz <paulswartz@gmail.com>
Date: Mon, 3 Aug 2009 12:13:43 -0400
Message-ID: <324cfb540908030913x71d331f0kb069052f74e5ae6b@mail.gmail.com>
Subject: Re: PyCrypto license clarification
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Status: RO
X-Status: A
Content-Length: 1450
On Sun, Aug 2, 2009 at 9:48 PM, Dwayne C. Litzenberger<dlitz@dlitz.net> wro=
te:
> Hi Paul,
>
> I am the new maintainer of the Python Cryptography Toolkit, and I am
> working on a new release at http://www.pycrypto.org/.
That's great!
> I understand that you have made contributions to PyCrypto, under nickname
> "z3p" and/or other names. =C2=A0May I, on your behalf, dedicate to the pu=
blic
> domain all your contributions to PyCrypto, with the following notice?
>
> =C2=A0=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
> =C2=A0The contents of this file are dedicated to the public domain. =C2=
=A0To the
> =C2=A0extent that dedication to the public domain is not available, every=
one
> =C2=A0is granted a worldwide, perpetual, royalty-free, non-exclusive lice=
nse
> =C2=A0to exercise all rights associated with the contents of this file fo=
r
> =C2=A0any purpose whatsoever. =C2=A0No rights are reserved.
> =C2=A0=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
Yes, that's fine. Good luck with the new release!
-p
--=20
Paul Swartz
paulswartz at gmail dot com
http://paulswartz.net/
AIM: z3penguin
From dlitz@dlitz.net Mon Aug 3 14:35:01 2009
Date: Mon, 3 Aug 2009 14:35:01 -0400
From: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
To: Paul Swartz <paulswartz@gmail.com>
Subject: Re: PyCrypto license clarification
Message-ID: <20090803183501.GA17472@rivest.dlitz.net>
References: <20090803014825.GA1326@rivest.dlitz.net> <324cfb540908030913x71d331f0kb069052f74e5ae6b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <324cfb540908030913x71d331f0kb069052f74e5ae6b@mail.gmail.com>
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: 1250
On Mon, Aug 03, 2009 at 12:13:43PM -0400, Paul Swartz wrote:
>On Sun, Aug 2, 2009 at 9:48 PM, Dwayne C. Litzenberger<dlitz@dlitz.net> wrote:
>> Hi Paul,
>>
>> I am the new maintainer of the Python Cryptography Toolkit, and I am
>> working on a new release at http://www.pycrypto.org/.
>
>That's great!
>
>> I understand that you have made contributions to PyCrypto, under nickname
>> "z3p" and/or other names.  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.
>>  =======================================================================
>
>Yes, that's fine. Good luck with the new release!
Perfect! Thanks for the quick response!
--
Dwayne C. Litzenberger <dlitz@dlitz.net>
Key-signing key - 19E1 1FE8 B3CF F273 ED17 4A24 928C EC13 39C2 5CF7

53
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Robey_Pointer.asc Normal file
View file

@ -0,0 +1,53 @@
Date: Mon, 16 Feb 2009 12:58:00 -0800
From: Robey Pointer <robey@lag.net>
Subject: Re: PyCrypto license clarification
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
Received-SPF: pass (goedel.dlitz.net: domain of robey@lag.net designates 69.61.78.186 as permitted sender)
Message-Id: <F469A078-6305-4484-BEA8-F4EC38A4154F@lag.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 23 Nov 2008, at 07:42, Dwayne C. Litzenberger wrote:
> 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, and he has approved the
> following dedication for his contributions.
>
> 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.
>
> =
> ======================================================================
>
In case I haven't replied to this yet: Yes, this is fine with me.
robey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAkmZ01gACgkQQQDkKvyJ6cOLvQCfQmYYuVODvIlyLg0hgCI9LAbQ
SH8AoLJgaq1lIi7/ZYDc+/Cd8VO0xLbr
=Mv6g
-----END PGP SIGNATURE-----

45
Cryptography/pycrypto-2.6.1/LEGAL/copy/stmts/Wim_Lewis.asc Normal file
View file

@ -0,0 +1,45 @@
Date: Sun, 23 Nov 2008 15:54:35 -0800
From: Wim Lewis <wiml@hhhh.org>
Subject: Re: PyCrypto license clarification
To: "Dwayne C. Litzenberger" <dlitz@dlitz.net>
Cc: Wim Lewis <wiml@hhhh.org>
Message-Id: <9D5C3135-7414-47D7-9D41-0AC6C3A84D97@hhhh.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On November 23, 2008, you wrote:
>Hi Wim,
>
>I am the new maintainer of the Python Cryptography Toolkit, and I am
>working on a new release at http://www.pycrypto.org/.
>
>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.
> =======================================================================
Certainly! I think the only code of mine in PyCrypto is the CAST-5 / CAST-128
implementation, which already has a public-domain notice at the top of
the file. But I am happy to have that, any any other code of mine that
might have wandered in there under an unclear open sourcish license,
distributed under the public-domain dedication you quote.
Wim.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (Darwin)
iQCVAwUBSSnnAl8UnN8n93LBAQLp/gQAhr7x8Av1mstc2kxEJDWTm26PTAZxMz4B
FektbDOzkxgc5580MGGeeX/MVn8aw+1BHg0YD85gsntlDzkcQtb+BR/xAvJ5zKyA
J/Mn/I+I6ekJQ3juh8IPHLAduOXM9Rtguas/yR+Doaq0xOPKoBx+/5+t1lLJtBcZ
wrPEa9Oui9s=
=zSY9
-----END PGP SIGNATURE-----