You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dp...@apache.org on 2019/06/18 11:48:22 UTC
[ignite] branch ignite-11932 updated: IGNITE-11932: Moved crypto
notice to README.txt file
This is an automated email from the ASF dual-hosted git repository.
dpavlov pushed a commit to branch ignite-11932
in repository https://gitbox.apache.org/repos/asf/ignite.git
The following commit(s) were added to refs/heads/ignite-11932 by this push:
new fa6b05a IGNITE-11932: Moved crypto notice to README.txt file
fa6b05a is described below
commit fa6b05ab08fe938cc5323cc0200b6eca2cb0eb1f
Author: Dmitriy Pavlov <dp...@apache.org>
AuthorDate: Tue Jun 18 14:48:01 2019 +0300
IGNITE-11932: Moved crypto notice to README.txt file
---
CRYPTO_NOTICE.txt | 47 -----------------------------------------------
README.txt | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 50 insertions(+), 47 deletions(-)
diff --git a/CRYPTO_NOTICE.txt b/CRYPTO_NOTICE.txt
deleted file mode 100644
index c5b3432..0000000
--- a/CRYPTO_NOTICE.txt
+++ /dev/null
@@ -1,47 +0,0 @@
-// Content of this notice should be copied to ./README.txt and (optionally) to ./README.md once it is ready
-== Crypto Notice
-
-This distribution includes cryptographic software. The country in
-which you currently reside may have restrictions on the import, possession,
-use, and/or re-export to another country, of encryption software.
-BEFORE using any encryption software, please check your country's laws,
-regulations and policies concerning the import, possession, or use,
-and re-export of encryption software, to see if this is permitted.
-See http://www.wassenaar.org/ for more information.
-
-The Apache Software Foundation has classified this software as Export
-Commodity Control Number (ECCN) 5D002, which includes information
-security software using or performing cryptographic functions with
-asymmetric algorithms. The form and manner of this Apache Software
-Foundation distribution makes it eligible for export under the
-"publicly available" Section 742.15(b) exemption (see the BIS Export
-Administration Regulations, Section 742.15(b)) for both object code
-and source code.
-
-The following provides more details on the included cryptographic software:
-
-- JDK SSL/TLS libraries used to enable secured connectivity between cluster
-nodes (https://apacheignite.readme.io/docs/ssltls).
-Oracle/OpenJDK (https://www.oracle.com/technetwork/java/javase/downloads/index.html)
-
-- JDK Java Cryptography Extensions build in encryption from the Java libraries is used
-for Transparent Data Encryption of data on disk
-(https://apacheignite.readme.io/docs/transparent-data-encryption).
-(https://java.sun.com/javase/technologies/security/)
-
-- Python client uses Python's SSL lib (https://docs.python.org/3/library/ssl.html) which is a wrapper over OpenSSL;
-- NodeJS client uses NodeJS's TLS module (https://nodejs.org/api/tls.html) which is a wrapper over OpenSSL;
-- PHP client uses PHP OpenSSL extension (https://www.php.net/manual/en/book.openssl.php);
-- C++ thin client and ODBC use OpenSSL to establish secure connection with the cluster.
-The OpenSSL Project (https://www.openssl.org/)
-
-- Apache Ignite SSH module requires the JSch library. This provides capabilities to
-start Apache Ignite nodes on remote machines via SSH.
-JCraft (http://www.jcraft.com/jsch/)
-
-- Apache Ignite REST http module requires Jetty, and this module can use HTTPs (uses SSL).
-Eclipse Jetty (http://eclipse.org/jetty)
-
-- Apache Ignite.NET uses .NET Framework crypto APIs from standard class library for all security and cryptographic related code.
- .NET Classic, Windows-only (https://dotnet.microsoft.com/download)
- .NET Core (https://dotnetfoundation.org/projects)
\ No newline at end of file
diff --git a/README.txt b/README.txt
index 2e6add5..34996f1 100644
--- a/README.txt
+++ b/README.txt
@@ -24,3 +24,53 @@ For information on how to get started with Apache Ignite please visit:
You can find Apache Ignite documentation here:
http://apacheignite.readme.io/docs
+
+
+Crypto Notice
+=============
+
+This distribution includes cryptographic software. The country in
+which you currently reside may have restrictions on the import, possession,
+use, and/or re-export to another country, of encryption software.
+BEFORE using any encryption software, please check your country's laws,
+regulations and policies concerning the import, possession, or use,
+and re-export of encryption software, to see if this is permitted.
+See http://www.wassenaar.org/ for more information.
+
+The Apache Software Foundation has classified this software as Export
+Commodity Control Number (ECCN) 5D002, which includes information
+security software using or performing cryptographic functions with
+asymmetric algorithms. The form and manner of this Apache Software
+Foundation distribution makes it eligible for export under the
+"publicly available" Section 742.15(b) exemption (see the BIS Export
+Administration Regulations, Section 742.15(b)) for both object code
+and source code.
+
+The following provides more details on the included cryptographic software:
+
+* JDK SSL/TLS libraries used to enable secured connectivity between cluster
+nodes (https://apacheignite.readme.io/docs/ssltls).
+Oracle/OpenJDK (https://www.oracle.com/technetwork/java/javase/downloads/index.html)
+
+* JDK Java Cryptography Extensions build in encryption from the Java libraries is used
+for Transparent Data Encryption of data on disk
+(https://apacheignite.readme.io/docs/transparent-data-encryption).
+(https://java.sun.com/javase/technologies/security/)
+
+* Python client uses Python's SSL lib (https://docs.python.org/3/library/ssl.html) which is a wrapper over OpenSSL;
+* NodeJS client uses NodeJS's TLS module (https://nodejs.org/api/tls.html) which is a wrapper over OpenSSL;
+* PHP client uses PHP OpenSSL extension (https://www.php.net/manual/en/book.openssl.php);
+* C++ thin client and ODBC use OpenSSL to establish secure connection with the cluster.
+The OpenSSL Project (https://www.openssl.org/)
+
+* Apache Ignite SSH module requires the JSch library. This provides capabilities to
+start Apache Ignite nodes on remote machines via SSH.
+JCraft (http://www.jcraft.com/jsch/)
+
+* Apache Ignite REST http module requires Jetty, and this module can use HTTPs (uses SSL).
+Eclipse Jetty (http://eclipse.org/jetty)
+
+* Apache Ignite.NET uses .NET Framework crypto APIs from standard class library
+for all security and cryptographic related code.
+ .NET Classic, Windows-only (https://dotnet.microsoft.com/download)
+ .NET Core (https://dotnetfoundation.org/projects)
\ No newline at end of file