You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Blake Bender (Jira)" <ji...@apache.org> on 2020/08/24 16:58:00 UTC

[jira] [Closed] (GEODE-8102) Link and load OpenSSL library directly

     [ https://issues.apache.org/jira/browse/GEODE-8102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Blake Bender closed GEODE-8102.
-------------------------------

> Link and load OpenSSL library directly
> --------------------------------------
>
>                 Key: GEODE-8102
>                 URL: https://issues.apache.org/jira/browse/GEODE-8102
>             Project: Geode
>          Issue Type: Improvement
>          Components: native client
>            Reporter: Jacob Barrett
>            Priority: Major
>              Labels: pull-request-available
>
> Lazy load the OpenSSL library directly, through ACE_SSL, into the apache-geode library. Currently we lazy load cryptoImpl, which immediately loads OpenSSL. The original intent was to avoid having an immediate dependency on OpenSSL at a time when its availability was questionable. On unix like systems OpenSSL is almost always available since so many other components in the OS depend on it. This immediate load dependency will have little to no effect on those systems. On some unix like systems the experience will improve by not having a runtime dependency on an intermediate library, cryptoImpl, that may need special treatments, like LD_LIBRARY_PATH or RPATH changes. On Windows, where OpenSSL is an anomaly we can use MSVC's lazy loading feature to only load OpenSSL if SSL/TLS is configured. This significantly improves the experience on Windows with regards to the location of cryptoImpl when using .NET.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)