You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by "Ernest Burghardt (JIRA)" <ji...@apache.org> on 2017/01/18 20:51:26 UTC
[jira] [Commented] (GEODE-2303) Review openssl linking
[ https://issues.apache.org/jira/browse/GEODE-2303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828753#comment-15828753 ]
Ernest Burghardt commented on GEODE-2303:
-----------------------------------------
Native Client does not link openssl; however, it does provide example code that when compiled (against user provided an openssl library) will link openssl.
The resulting example library (we call securityImpl) can be dynamically loaded at runtime; see the "security quickstarts".
Native Client does not link openssl into any binary, but has the capability to utilize cryptography, which [~jbarrett] tells me qualifies to have an ECCN.
Given this is apart of geode, we should be able to just use geode's ECCN.
> Review openssl linking
> ----------------------
>
> Key: GEODE-2303
> URL: https://issues.apache.org/jira/browse/GEODE-2303
> Project: Geode
> Issue Type: Sub-task
> Components: native client
> Reporter: Anthony Baker
>
> Since we link to the openssl library, we should assess whether an ECCN is required.
> https://www.apache.org/licenses/exports/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)