Re: disabled SSL log_like tests

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <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-07 04:58:03
Message-ID: CA+hUKGLO=rq8iy0zwLHO9Kxv=vsB+b=XQg0Wn9TunuQj1=v5Bw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 7, 2025 at 4:34 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thanks, I'll look into reporting it tomorrow. In the meantime,
> I couldn't help noticing that the backtraces went through
> lib/libssl/tls13_legacy.c, which doesn't give a warm feeling
> about how supported they think our usage is (and perhaps also
> explains why they didn't detect this bug themselves). This is
> evidently because we set up the SSL context with SSLv23_method(),
> per this comment in be_tls_init():

Oh, interesting. I also wondered if the problem I reported might be
related to the separate legacy code paths in x509_vfy.c.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message shveta malik 2025-05-07 05:01:55 Re: Fix slot synchronization with two_phase decoding enabled
Previous Message Andrei Lepikhov 2025-05-07 04:39:09 Incorrect calculation of path fraction value in MergeAppend