Re: OpenSSL 3.0.0 compatibility

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2020-06-02 08:57:40
Message-ID: 504df292-50a7-2a6b-d366-a3772c273421@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-06-01 15:23, Andrew Dunstan wrote:
>
> On 6/1/20 8:03 AM, Daniel Gustafsson wrote:
>>> On 1 Jun 2020, at 13:58, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>>> If you want I can add a rule for it to the Makefile, although who knows
>>> what commands will actually apply when the certificate runs out?
>> Being able to easily regenerate the testdata, regardless of expiration status,
>> has proven very helpful for me when implementing support for new TLS backends.
>> +1 for adding it to the Makefile.
>>
> OK, here's a patch.

In src/test/ssl/ we have targets sslfiles and sslfiles-clean, and here
we have ssl-files and ssl-files-clean. Let's keep that consistent.

Or, why not actually use the generated files from src/test/ssl/ instead
of making another set?

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-06-02 09:04:42 Re: Expand the use of check_canonical_path() for more GUCs
Previous Message Amit Kapila 2020-06-02 08:42:37 Re: elog(DEBUG2 in SpinLocked section.