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)