pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feedlippq client library and openssl initialization: PQinitOpenSSL()
11+ messages / 5 participants
[nested] [flat]
Commits from this thread:
2023-04-14 928e05ddfd de575c78e1 e9884e9921 36f49be808 e76fbcf796 ea7894d33d doc: PQinitOpenSSL and PQinitSSL are obsolete in OpenSSL 1.1.0+
* lippq client library and openssl initialization: PQinitOpenSSL()
@ 2022-09-11 10:55 Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 13:58 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Jeffrey Walton <noloader@gmail.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 2 replies; 11+ messages in thread
From: Sebastien Flaesch @ 2022-09-11 10:55 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Hello!
The PostgreSQL doc says that if the application code is initializing OpenSSL, it should tell PostgreSQL libpq client library that 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+
The APIs to initialize OpenSSL are OPENSSL_init_ssl() or OPENSSL_init_crypto().
According to the OpenSSL doc, version 1.1.0 initializes itself automatically when calling other APIs ...
https://www.openssl.org/docs/man1.1.1/man3/OPENSSL_init_ssl.html
As of version 1.1.0 OpenSSL will automatically allocate all resources that it needs so no explicit initialisation is required. Similarly it will also automatically deinitialise as required.
So, is a call to PQinitOpenSSL(0, 0) still needed?
I did some test with our application, and I could establish a TLS/SSL connection using server and client certificates.
What can go wrong in fact?
Can someone give me a hint, so I can prove that we really need to call PQinitOpenSSL(0,0)?
Note: Our application is for now single-threaded.
OpenSSL doc also states:
However, there may be situations when explicit initialisation is desirable or needed, for example when some nondefault initialisation is required.
If our application would requires nondefault initialization, I assume that PostgreSQL openssl usage will implicitly inherit the OpenSSL seetings of our application, right?
Can this be an issue for PostgreSQL, or can both just share the same OpenSSL settings/config?
Thanks!
Seb
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
@ 2022-09-11 13:58 ` Jeffrey Walton <noloader@gmail.com>
1 sibling, 0 replies; 11+ messages in thread
From: Jeffrey Walton @ 2022-09-11 13:58 UTC (permalink / raw)
To: Sebastien Flaesch <sebastien.flaesch@4js.com>; +Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
On Sun, Sep 11, 2022 at 6:55 AM Sebastien Flaesch
<sebastien.flaesch@4js.com> wrote:
>
> The PostgreSQL doc says that if the application code is initializing OpenSSL, it should tell PostgreSQL libpq client library that 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+
>
> The APIs to initialize OpenSSL are OPENSSL_init_ssl() or OPENSSL_init_crypto().
>
> According to the OpenSSL doc, version 1.1.0 initializes itself automatically when calling other APIs ...
>
> https://www.openssl.org/docs/man1.1.1/man3/OPENSSL_init_ssl.html
>
> As of version 1.1.0 OpenSSL will automatically allocate all resources that it needs so no explicit initialisation is required. Similarly it will also automatically deinitialise as required.
>
> So, is a call to PQinitOpenSSL(0, 0) still needed?
>
> I did some test with our application, and I could establish a TLS/SSL connection using server and client certificates.
>
> What can go wrong in fact?
>
> Can someone give me a hint, so I can prove that we really need to call PQinitOpenSSL(0,0)?
>
> Note: Our application is for now single-threaded.
>
> OpenSSL doc also states:
>
> However, there may be situations when explicit initialisation is desirable or needed, for example when some nondefault initialisation is required.
>
> If our application would requires nondefault initialization, I assume that PostgreSQL openssl usage will implicitly inherit the OpenSSL seetings of our application, right?
>
> Can this be an issue for PostgreSQL, or can both just share the same OpenSSL settings/config?
For the OpenSSL side of things, then see
https://wiki.openssl.org/index.php/Library_Initialization .
Jeff
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
@ 2022-09-11 15:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
1 sibling, 1 reply; 11+ messages in thread
From: Tom Lane @ 2022-09-11 15:08 UTC (permalink / raw)
To: Sebastien Flaesch <sebastien.flaesch@4js.com>; +Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
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 library that 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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
@ 2022-09-11 20:57 ` Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Gustafsson @ 2022-09-11 20:57 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
> On 11 Sep 2022, at 17:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> 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 library that 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.
To the best of my knowledge, thats entirely correct.
--
Daniel Gustafsson https://vmware.com/
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
@ 2022-09-11 21:35 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
0 siblings, 1 reply; 11+ messages in thread
From: Tom Lane @ 2022-09-11 21:35 UTC (permalink / raw)
To: Daniel Gustafsson <daniel@yesql.se>; +Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Daniel Gustafsson <daniel@yesql.se> writes:
> On 11 Sep 2022, at 17:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.
> To the best of my knowledge, thats entirely correct.
Should we document these functions as obsolete when using
OpenSSL >= 1.1.0 ?
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
@ 2022-09-11 21:43 ` Daniel Gustafsson <daniel@yesql.se>
2022-09-12 11:21 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Peter Eisentraut <peter.eisentraut@enterprisedb.com>
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Gustafsson @ 2022-09-11 21:43 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
> On 11 Sep 2022, at 23:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.se> writes:
>> On 11 Sep 2022, at 17:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> 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.
>
>> To the best of my knowledge, thats entirely correct.
>
> Should we document these functions as obsolete when using
> OpenSSL >= 1.1.0 ?
Given that 1.1.0+ is very common, it's probably not a bad idea to document them
as obsolete but harmless. Unless you beat me to it I can propose a patch.
--
Daniel Gustafsson https://vmware.com/
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
@ 2022-09-12 11:21 ` Peter Eisentraut <peter.eisentraut@enterprisedb.com>
2022-09-12 11:55 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
0 siblings, 1 reply; 11+ messages in thread
From: Peter Eisentraut @ 2022-09-12 11:21 UTC (permalink / raw)
To: Daniel Gustafsson <daniel@yesql.se>; Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
On 11.09.22 23:43, Daniel Gustafsson wrote:
>> On 11 Sep 2022, at 23:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> Daniel Gustafsson <daniel@yesql.se> writes:
>>> On 11 Sep 2022, at 17:08, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>>> 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.
>>
>>> To the best of my knowledge, thats entirely correct.
>>
>> Should we document these functions as obsolete when using
>> OpenSSL >= 1.1.0 ?
>
> Given that 1.1.0+ is very common, it's probably not a bad idea to document them
> as obsolete but harmless. Unless you beat me to it I can propose a patch.
AFAICT, RHEL 7 ships with an older version. I think that's still pretty
widespread.
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-12 11:21 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Peter Eisentraut <peter.eisentraut@enterprisedb.com>
@ 2022-09-12 11:55 ` Daniel Gustafsson <daniel@yesql.se>
2022-09-12 13:47 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Gustafsson @ 2022-09-12 11:55 UTC (permalink / raw)
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>; +Cc: Tom Lane <tgl@sss.pgh.pa.us>; Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
> On 12 Sep 2022, at 13:21, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
> On 11.09.22 23:43, Daniel Gustafsson wrote:
>>> On 11 Sep 2022, at 23:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Should we document these functions as obsolete when using
>>> OpenSSL >= 1.1.0 ?
>> Given that 1.1.0+ is very common, it's probably not a bad idea to document them
>> as obsolete but harmless. Unless you beat me to it I can propose a patch.
>
> AFAICT, RHEL 7 ships with an older version. I think that's still pretty widespread.
Fair enough. That doesn't however IMO prevent us from adding a note that 1.1.0
and onwards are different. The attached keeps the strong wording of the main
para, but adds a note after the related functions.
--
Daniel Gustafsson https://vmware.com/
Attachments:
pqinitopenssl.diff (application/octet-stream, 532B) download
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 8a1a9e9932..6570190dc1 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -8787,6 +8787,13 @@ void PQinitSSL(int do_ssl);
</listitem>
</varlistentry>
</variablelist>
+ <note>
+ <para>
+ OpenSSL 1.1.0 and later performs initialization automatically, and
+ <literal>PQinitOpenSSL</literal> is no longer required, but can still
+ be used for backwards compatibility.
+ </para>
+ </note>
</para>
</sect2>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-12 11:21 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Peter Eisentraut <peter.eisentraut@enterprisedb.com>
2022-09-12 11:55 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
@ 2022-09-12 13:47 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-04-12 10:59 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
0 siblings, 1 reply; 11+ messages in thread
From: Tom Lane @ 2022-09-12 13:47 UTC (permalink / raw)
To: Daniel Gustafsson <daniel@yesql.se>; +Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>; Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Daniel Gustafsson <daniel@yesql.se> writes:
> On 12 Sep 2022, at 13:21, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>> AFAICT, RHEL 7 ships with an older version. I think that's still pretty widespread.
> Fair enough. That doesn't however IMO prevent us from adding a note that 1.1.0
> and onwards are different. The attached keeps the strong wording of the main
> para, but adds a note after the related functions.
Personally I'd put this up front, more like
have been initialized by your application, so that
<application>libpq</application> will not also initialize those libraries.
+ However, this is unnecessary when using OpenSSL 1.1.0 or later,
+ as duplicate initializations are no longer problematic.
</para>
If you do use wording that specifically mentions PQinitOpenSSL,
it should also mention PQinitSSL, just for clarity.
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-12 11:21 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Peter Eisentraut <peter.eisentraut@enterprisedb.com>
2022-09-12 11:55 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-12 13:47 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
@ 2023-04-12 10:59 ` Daniel Gustafsson <daniel@yesql.se>
2023-04-12 12:04 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 11+ messages in thread
From: Daniel Gustafsson @ 2023-04-12 10:59 UTC (permalink / raw)
To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>; Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
> On 12 Sep 2022, at 15:47, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Personally I'd put this up front, more like
>
> have been initialized by your application, so that
> <application>libpq</application> will not also initialize those libraries.
> + However, this is unnecessary when using OpenSSL 1.1.0 or later,
> + as duplicate initializations are no longer problematic.
> </para>
>
> If you do use wording that specifically mentions PQinitOpenSSL,
> it should also mention PQinitSSL, just for clarity.
Reviving an old thread that got buried, I propose to apply the attached and
backpatch it as OpenSSL of such vintage is equally likely to be used in old
versions of postgres as current.
--
Daniel Gustafsson
Attachments:
pqinitopenssl_v2.diff (application/octet-stream, 662B) download
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index faa8aa3187..2e0d3d6353 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -9000,6 +9000,8 @@ ldap://ldap.acme.com/cn=dbserver,cn=hosts?pgconnectinfo?base?(objectclass=*)
that the <literal>libssl</literal> and/or <literal>libcrypto</literal> libraries
have been initialized by your application, so that
<application>libpq</application> will not also initialize those libraries.
+ However, this is unnecessary when using <productname>OpenSSL</productname>
+ version 1.1.0 or later, as duplicate initializations are no longer problematic.
</para>
<para>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: lippq client library and openssl initialization: PQinitOpenSSL()
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 15:08 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-12 11:21 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Peter Eisentraut <peter.eisentraut@enterprisedb.com>
2022-09-12 11:55 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
2022-09-12 13:47 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Tom Lane <tgl@sss.pgh.pa.us>
2023-04-12 10:59 ` Re: lippq client library and openssl initialization: PQinitOpenSSL() Daniel Gustafsson <daniel@yesql.se>
@ 2023-04-12 12:04 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 11+ messages in thread
From: Tom Lane @ 2023-04-12 12:04 UTC (permalink / raw)
To: Daniel Gustafsson <daniel@yesql.se>; +Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>; Sebastien Flaesch <sebastien.flaesch@4js.com>; pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Daniel Gustafsson <daniel@yesql.se> writes:
> Reviving an old thread that got buried, I propose to apply the attached and
> backpatch it as OpenSSL of such vintage is equally likely to be used in old
> versions of postgres as current.
+1
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2023-04-12 12:04 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-09-11 10:55 lippq client library and openssl initialization: PQinitOpenSSL() Sebastien Flaesch <sebastien.flaesch@4js.com>
2022-09-11 13:58 ` Jeffrey Walton <noloader@gmail.com>
2022-09-11 15:08 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 20:57 ` Daniel Gustafsson <daniel@yesql.se>
2022-09-11 21:35 ` Tom Lane <tgl@sss.pgh.pa.us>
2022-09-11 21:43 ` Daniel Gustafsson <daniel@yesql.se>
2022-09-12 11:21 ` Peter Eisentraut <peter.eisentraut@enterprisedb.com>
2022-09-12 11:55 ` Daniel Gustafsson <daniel@yesql.se>
2022-09-12 13:47 ` Tom Lane <tgl@sss.pgh.pa.us>
2023-04-12 10:59 ` Daniel Gustafsson <daniel@yesql.se>
2023-04-12 12:04 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox