Re: Improve errors when setting incorrect bounds for SSL protocols

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Improve errors when setting incorrect bounds for SSL protocols
Date: 2020-02-06 22:30:40
Message-ID: 5467709A-F3D3-4FD6-800D-7DC8C2FB27BB@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 6 Feb 2020, at 20:04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I think this should be reverted. Perhaps there's a way to do it without
> these problems, but we failed to find one in the past.

Or change to the v1 patch in this thread, which avoids the problem by doing it
in the OpenSSL code. It's a shame to have generic TLS functionality be OpenSSL
specific when everything else TLS has been abstracted, but not working is
clearly a worse option.

cheers ./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2020-02-06 23:38:27 Getting rid of some more lseek() calls
Previous Message Peter Geoghegan 2020-02-06 21:45:11 Re: Memory-Bounded Hash Aggregation