Legal: Add public domain dedication from Mark Moraes

Thanks, Mark!

1 files changed, 340 insertions, 0 deletions

diff --git a/LEGAL/copy/stmts/Mark_Moraes.mbox b/LEGAL/copy/stmts/Mark_Moraes.mbox
new file mode 100644
index 0000000..11cb715
--- /dev/null
+++ b/LEGAL/copy/stmts/Mark_Moraes.mbox
@@ -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
+