From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Victor Wagner <vitus(at)wagner(dot)pp(dot)ru>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL12 and older versions of OpenSSL |
Date: | 2019-09-27 01:51:01 |
Message-ID: | 20190927015101.GC2078@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 26, 2019 at 06:24:22PM +0200, Peter Eisentraut wrote:
> Here is my proposed patch, currently completely untested.
I have tested compilation of REL_12_STABLE with the top of OpenSSL
0.9.8, 1.0.0, 1.0.1, 1.0.2, 1.1.0 and 1.1.1. Our SSL tests also pass
in all the setups I have tested.
Your patch does not issue a ereport(LOG/FATAL) in the event of a
failure with SSL_CTX_set_max_proto_version(), which is something done
when ssl_protocol_version_to_openssl()'s result is -1. Wouldn't it be
better to report that properly to the user?
Some more nits about the patch I have. Would it be worth copying the
comment from min_proto_version() to SSL_CTX_set_max_proto_version()?
I would add a newline before the comment block as well.
Note: We have a failure with ssl/t/002_scram.pl because of the
introduction of the recent channel_binding parameter if you try to run
the SSL tests on HEAD with at least 0.9.8 as we forgot to add a
conditional check for HAVE_X509_GET_SIGNATURE_NID as c3d41cc did.
I'll send a patch for that separately. That's why I have checked the
patch only with REL_12_STABLE.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2019-09-27 02:20:51 | tab complete for explain SETTINGS |
Previous Message | Alvaro Herrera | 2019-09-27 01:22:13 | Re: [PATCH] Race condition in logical walsender causes long postgresql shutdown delay |