Re: Fix error handling in be_tls_open_server()

From: Jacob Champion <jchampion(at)timescale(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>, Daniel Gustafsson <daniel(at)yesql(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Fix error handling in be_tls_open_server()
Date: 2023-08-28 15:12:45
Message-ID: CAAWbhmgkWUsDHaVfX5RD7WRPWFiY17AbQgYWwPBqh6nhEy=Piw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 24, 2023 at 6:25 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> LD_PRELOAD is the only thing I can think about, but that's very fancy.
> Even with that, having a certificate with a NULL peer_cn could prove
> to be useful in the SSL suite to stress more patterns around it?

+1. Last we tried it, OpenSSL didn't want to create a certificate with
an embedded null, but maybe things have changed?

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-08-28 15:14:13 Re: Disabling Heap-Only Tuples
Previous Message Masahiko Sawada 2023-08-28 14:43:22 Re: [PoC] Improve dead tuple storage for lazy vacuum