Re: OpenSSL 3.0.0 compatibility

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2020-06-01 13:23:24
Message-ID: 03e89ff7-8459-0800-e12f-41c38fd8a205@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
ssl-passphase-callback-certs.patch text/x-patch 958 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kenichiro Tanaka 2020-06-01 13:35:02 Wrong width of UNION statement
Previous Message Daniel Gustafsson 2020-06-01 12:03:38 Re: OpenSSL 3.0.0 compatibility