Re: lippq client library and openssl initialization: PQinitOpenSSL() - Mailing list pgsql-general

From Tom Lane
Subject Re: lippq client library and openssl initialization: PQinitOpenSSL()
Date
Msg-id 816006.1662908880@sss.pgh.pa.us
Whole thread Raw
In response to lippq client library and openssl initialization: PQinitOpenSSL()  (Sebastien Flaesch <sebastien.flaesch@4js.com>)
Responses Re: lippq client library and openssl initialization: PQinitOpenSSL()
List pgsql-general
Sebastien Flaesch <sebastien.flaesch@4js.com> writes:
> The PostgreSQL doc says that if the application code is initializing OpenSSL, it should tell PostgreSQL libpq client
librarythat OpenSSL initialization is already done: 
> https://www.postgresql.org/docs/14/libpq-ssl.html#LIBPQ-SSL-INITIALIZE
> I was wondering if this is still true with OpenSSL 1.1.0+

Don't believe so.  The HAVE_CRYPTO_LOCK stuff is all obsolete and
not compiled if you built against 1.1.0.  The only thing left that
will happen if you don't call PQinitOpenSSL is an extra call to
OPENSSL_init_ssl, which should be harmless as far as I can see
from the OpenSSL docs.

            regards, tom lane



pgsql-general by date:

Previous
From: Jeffrey Walton
Date:
Subject: Re: lippq client library and openssl initialization: PQinitOpenSSL()
Next
From: Junwang Zhao
Date:
Subject: Re: [EXT] Re: log_min_messages = warning