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>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Setting min/max TLS protocol in clientside libpq
Date: 2020-01-24 11:19:31
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> On 17 Jan 2020, at 03:38, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Fri, Jan 17, 2020 at 10:09:54AM +0900, Michael Paquier wrote:
>> Could you please rebase and fix the remaining pieces of the patch?
> And while I remember, you may want to add checks for incorrect bounds
> when validating the values in fe-connect.c... The same arguments as
> for the backend part apply because we'd want to make the
> implementation a maximum pluggable with all SSL libraries.


Attached is a v5 of the patch which hopefully address all the comments raised,
sorry for the delay.

cheers ./daniel

Attachment Content-Type Size
libpq_minmaxproto_v5.patch application/octet-stream 14.7 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2020-01-24 11:25:06 Re: Add support for automatically updating Unicode derived files
Previous Message Fabien COELHO 2020-01-24 10:56:27 Re: [PoC] Non-volatile WAL buffer