Re: lippq client library and openssl initialization: PQinitOpenSSL()
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
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>
Date: 2022-09-12T11:55:29Z
Lists: pgsql-general
Attachments
- pqinitopenssl.diff (application/octet-stream) patch
> 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/
Commits
-
doc: PQinitOpenSSL and PQinitSSL are obsolete in OpenSSL 1.1.0+
- ea7894d33d17 11.20 landed
- e76fbcf796d6 12.15 landed
- 36f49be80856 13.11 landed
- e9884e992186 14.8 landed
- de575c78e14c 15.3 landed
- 928e05ddfd40 16.0 landed