Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Jacob Champion <jchampion(at)timescale(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Date: 2023-06-02 08:35:43
Message-ID: BFEF8322-ADE6-44E0-973F-04540CEAC660@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 27 May 2023, at 04:02, Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> Making the build fail straight when setting up things is OK
> by me, but I am not convinced that X509_get_signature_nid() would be
> the right choice for the job, as it is an OpenSSL artifact originally,
> AFAIK.

I think we should avoid the is-defined-in dance and just pull out the version
numbers for comparisons. While it's true that LibreSSL doesn't play well with
OpenSSL versions, they do define their own which can be checked for to
distinguish the libraries.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2023-06-02 12:16:16 Re: [BUG] pg_dump does not properly deal with BEGIN ATOMIC function
Previous Message Ants Aasma 2023-06-02 08:01:42 Re: Do we want a hashset type?