| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: settings to control SSL/TLS protocol version |
| Date: | 2018-10-02 12:23:06 |
| Message-ID: | 0a4c4605-923f-690f-f8b0-b6b185ebcf04@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 01/10/2018 23:30, Daniel Gustafsson wrote:
>> ssl_min_protocol_version = 'TLSv1'
>> ssl_max_protocol_version = ‘any'
>
> I don’t think ‘any’ is a clear name for a setting which means “the highest
> supported version”. How about ‘max_supported’ or something similar?
I can see the argument for an alternative, but your suggestion is a
mouthful.
> +1 for using a min/max approach for setting the version, and it should be
> trivial to add support for in the pending GnuTLS and Secure Transport patches.
AFAICT, in GnuTLS this is done via the "priorities" setting that also
sets the ciphers. There is no separate API for just the TLS version.
It would be interesting to see how Secure Transport can do it.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2018-10-02 12:29:14 | Re: settings to control SSL/TLS protocol version |
| Previous Message | Andrew Dunstan | 2018-10-02 12:21:30 | Re: pg_ls_tmpdir() |