[
https://issues.apache.org/jira/browse/KUDU-1738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840547#comment-15840547
]
Todd Lipcon commented on KUDU-1738:
-----------------------------------
I think the global one like you suggested is what we were going for.
I believe we are already initializing OpenSSL in our client, but it may be that
we only do so lazily if connecting to a TLS-enabled Kudu cluster... so either
this is already biting us (but is a rare race that isn't likely to happen) or
it's going to bite us soon when we start connecting to kudu with TLS. I'd say
either way we should go ahead and do it, because we know it's a good idea.
> Allow users of C++ client to disable initialization of OpenSSL
> --------------------------------------------------------------
>
> Key: KUDU-1738
> URL: https://issues.apache.org/jira/browse/KUDU-1738
> Project: Kudu
> Issue Type: Bug
> Components: client, security
> Affects Versions: 1.1.0
> Reporter: Todd Lipcon
>
> As we start to use OpenSSL from within the client, we now take care of
> initializing the OpenSSL library. Programs which embed us may have already
> initialized OpenSSL for their own purposes. In that case, we don't want Kudu
> to run the initialization a second time.
> We should probably add some kind of option to KuduClientBuilder which
> disables the SSL initialization. Another thought is that we may want to
> detect if the SSL library has already been initialized and automatically
> skip. (it seems this is possible by calling SSL_CTX_new and checking the
> error code to see if it's not initialized yet)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
