Re: Setting min/max TLS protocol in clientside libpq

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, cary huang <hcary328(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Setting min/max TLS protocol in clientside libpq
Date: 2020-01-28 10:29:39
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 28 Jan 2020, at 04:53, Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> Now, we already mention in the docs which values the min and max
> bounds support, and that the version of OpenSSL used by the backend
> and the frontend are impacted by that depending on what version of
> OpenSSL one or the other link to. The remaining piece is that the
> client and the server negotiate the protocol they use, which is an
> obvious fact, at least to me..

You don't really qualify as the target audience for basic, yet not always
universally known/understood, sections in the documentation though =) I've
heard enough complaints that it's complicated to set up that I think we need to
make the docs more digestable, but if noone else +1's then lets drop it.

cheers ./daniel

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2020-01-28 10:44:08 ReadRecord wrongly assumes randAccess after 38a957316d.
Previous Message Thomas Munro 2020-01-28 09:56:26 Re: The flinfo->fn_extra question, from me this time.