geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pivotal-jbarrett <>
Subject [GitHub] geode-native pull request #95: GEODE-2832: Fixing the link of
Date Fri, 05 May 2017 14:19:51 GMT
Github user pivotal-jbarrett commented on a diff in the pull request:
    --- Diff: ---
    @@ -24,3 +24,33 @@ Native Client applications can be written in these client technologies:
     * [C++](
     * [C#](
    +## Export Control
    +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 <> for more information.
    +The U.S. Government Department of Commerce, Bureau of Industry and Security (BIS),
    +has classified this software as Export Commodity Control Number (ECCN) 5D002.C.1,
    +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 License Exception
    +ENC Technology Software Unrestricted (TSU) exception
    +(see the BIS Export Administration Regulations, Section 740.13)
    +for both object code and source code.
    +The following provides more details on the included cryptographic software:
    +* Apache Geode is designed to be used with
    +  [Java Secure Socket Extension](
(JSSE) and
    --- End diff --
    This README is for geode-native. It does not run in Java and therefor should not have
the statements about JCE.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message