| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Steven Fackler <sfackler(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Supporting tls-server-end-point as SCRAM channel binding for OpenSSL 1.0.0 and 1.0.1 |
| Date: | 2018-06-27 16:49:10 |
| Message-ID: | 15d35905-6028-3b09-88af-d64b6619e525@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/23/18 17:09, Bruce Momjian wrote:
> On Wed, Jun 6, 2018 at 01:16:11PM -0700, Steven Fackler wrote:
>> TLS 1.3, (which is currently in a draft state, but is theoretically being
>> finalized soon) does not support the TLS channel binding algorithms [1]. From
>
> Uh, according to this article, TLS 1.3 was finalized in March:
>
> https://www.theregister.co.uk/2018/03/27/with_tls_13_signed_off_its_implementation_time/
More generally, is our TLS 1.3 support sound? For instance, I've read
about new cipher suites, so one question is, do the existing
configuration settings that control such things even still work?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-06-27 16:51:02 | Re: assert in nested SQL procedure call in current HEAD |
| Previous Message | Konstantin Knizhnik | 2018-06-27 16:32:18 | Monitoring time of fsyncing WALs |