[ignite] branch ignite-11932 updated: IGNITE-11932: jetty related updates to crypto notice.

[dp...@apache.org]

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 8348611  IGNITE-11932: jetty related updates to crypto notice.
8348611 is described below

commit 834861182dc71f012591d4c21cb12ef94cbd19c4
Author: Dmitriy Pavlov <dp...@apache.org>
AuthorDate: Tue Jun 18 14:40:31 2019 +0300

    IGNITE-11932: jetty related updates to crypto notice.
---
 CRYPTO_NOTICE.txt | 11 +++++++----
 eccn_update.xml   |  1 -
 2 files changed, 7 insertions(+), 5 deletions(-)

diff --git a/CRYPTO_NOTICE.txt b/CRYPTO_NOTICE.txt
index d7a0206..c5b3432 100644
--- a/CRYPTO_NOTICE.txt
+++ b/CRYPTO_NOTICE.txt
@@ -21,24 +21,27 @@ 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 )
-Manufacturer - Oracle/OpenJDK (https://www.oracle.com/technetwork/java/javase/downloads/index.html)
+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://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/
+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/eccn_update.xml b/eccn_update.xml
index 6eb847b..8b4bd5c 100644
--- a/eccn_update.xml
+++ b/eccn_update.xml
@@ -43,7 +43,6 @@ No need to merge it to Apache Ignite code base.
                 <Manufacturer>JCraft, Inc.</Manufacturer>
                 <Why>Provides encryption SSH library</Why>
             </ControlledSource>
-            <!-- TODO: Confirm that REST-HTTP module can use HTTPS itself, or remove -->
             <ControlledSource href="http://eclipse.org/jetty">
                 <Manufacturer>The Eclipse Foundation</Manufacturer>
                 <Why>HTTPS support in Jetty (uses SSL)</Why>