From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
Subject: | Re: disabled SSL log_like tests |
Date: | 2025-05-09 07:24:57 |
Message-ID: | EAF11543-5526-40FB-A039-D07A010DF84A@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 9 May 2025, at 02:15, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> If we were to end up with a
>> Libressl libtls implementation in libpq we'd still have to test with Libressl
>> against the OpenSSL compat layer in libssl since it could act as both. Not a
>> bridge we have to cross today but might be worth at least keeping in mind when
>> designing something to not make it impossible in the future.
>
> Right. I think the attached would be amenable to that.
It will be a bit awkward to ask "are you libressl" if we ever add support for
something not OpenSSL based, but we could always revisit should that happen.
> Further down the road, it seems inevitable that we'll need to have a
> way of detecting the SSL library version --- for example, assuming
> the LibreSSL folk eventually fix their RSA-PSS code, we'll need a
> version-dependent test. That could be another new backend method,
> I guess.
Agreed.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Dolgov | 2025-05-09 08:10:46 | Re: queryId constant squashing does not support prepared statements |
Previous Message | Michael Paquier | 2025-05-09 06:58:42 | Re: Support for runtime parameters in injection points, for AIO tests |