summaryrefslogtreecommitdiff
path: root/LEGAL
diff options
context:
space:
mode:
authorDwayne C. Litzenberger <dlitz@dlitz.net>2009-08-03 20:23:19 -0400
committerDwayne C. Litzenberger <dlitz@dlitz.net>2009-08-03 20:24:34 -0400
commit9df50513c6d401656d26c87937c63b6e9e77a0df (patch)
tree3c24a0ca243a1b5b0040334e4871e9b6a8b4f5b6 /LEGAL
parent462069263ca6e3c4fac53351a34391e6cef5a7e7 (diff)
downloadpycrypto-9df50513c6d401656d26c87937c63b6e9e77a0df.tar.gz
Move LEGAL/copy/README to COPYRIGHT and update it.
Diffstat (limited to 'LEGAL')
-rw-r--r--LEGAL/copy/00INDEX1
-rw-r--r--LEGAL/copy/README29
2 files changed, 0 insertions, 30 deletions
diff --git a/LEGAL/copy/00INDEX b/LEGAL/copy/00INDEX
index ee7c0a8..fbdca18 100644
--- a/LEGAL/copy/00INDEX
+++ b/LEGAL/copy/00INDEX
@@ -1,5 +1,4 @@
00INDEX This file
-README Information about the files in this directory.
LICENSE.orig Original (deprecated) license for the Python Cryptography Toolkit
LICENSE.libtom LICENSE file from LibTomCrypt
stmts/ Statements by contributors
diff --git a/LEGAL/copy/README b/LEGAL/copy/README
deleted file mode 100644
index f794720..0000000
--- a/LEGAL/copy/README
+++ /dev/null
@@ -1,29 +0,0 @@
-Historically, the copyright licensing status of the Python Cryptography
-Toolkit ("PyCrypto") has been somewhat ambiguous. The original intention of
-Andrew M. Kuchling and other contributors has been to dedicate PyCrypto to the
-public domain, but the original license may not have allowed distributing
-modified versions, depending on one's interpretation of the word "use" (see
-LICENSE.orig).
-
-Additionally, some files within PyCrypto have specified their own licenses,
-which differed from the PyCrypto license itself. For example, the original
-RIPEMD.c module simply had a copyright statement and warranty disclaimer,
-without clearly licensing anything.
-
-Recently, there has been an effort to clarify the situation. A multi-faceted
-approach has been taken with regard to ambiguously or incompatibly licensed
-code, including:
-
-- Asking contributors to clarify their original intentions or to clearly and
- explicitly dedicate their contributions to the public domain;
-
-- Writing new code from scratch as a replacement;
-
-- Using clearly-licensed code from other sources; and
-
-- Removing the code without replacing it.
-
-Where contributors have responded to a request to clarify their intentions,
-their statements have been recorded in this directory.
-
-The "stmts" directory contains contributors' statements.