File Manager

Editing File: /usr/share/licenses/python-crypto/LEGAL/copy/stmts/Joris_Bontje.mbox

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

Back to Directory File Manager