Re: OpenSSL 3.0.0 compatibility - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: OpenSSL 3.0.0 compatibility
Date
Msg-id 504df292-50a7-2a6b-d366-a3772c273421@2ndquadrant.com
Whole thread Raw
In response to Re: OpenSSL 3.0.0 compatibility  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: OpenSSL 3.0.0 compatibility  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List 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.dunstan@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: elog(DEBUG2 in SpinLocked section.
Next
From: Peter Eisentraut
Date:
Subject: Re: Expand the use of check_canonical_path() for more GUCs