Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com>
Cc: benjamin(dot)arthur(dot)mejia(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Daniel Gustafsson <daniel(at)yesql(dot)se>
Subject: Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
Date: 2026-10-30 19:47:17
Message-ID: CAOYmi+kTVNvy1PvJTJyDQu4oL69ria4HLYwWggiGguNkjto_BQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Oct 30, 2026 at 12:10 PM Andrey Rachitskiy <pl0h0yp1(at)gmail(dot)com> wrote:
> OpenSSL 1.1.1 has no mapping for missing_extension and returns -1 [1]. ssl3_send_alert() writes nothing [2], the socket closes and libpq reports "SSL SYSCALL error: EOF detected".

1.1.1o apparently fixes the mapping behavior, which is why I didn't
see it locally... It's easy enough to add an alternative expected
message to the tests, but why aren't our RHEL 8 buildfarm machines
complaining?

--Jacob

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey Rachitskiy 2026-10-30 19:59:23 Re: BUG #19815: 004_sni.pl fails deterministically with OpenSSL 1.1.1 (tests 75 and 86)
Previous Message Tom Lane 2026-10-30 19:32:29 Re: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed