Re: Direct SSL connection with ALPN and HBA rules

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Direct SSL connection with ALPN and HBA rules
Date: 2024-05-16 14:08:14
Message-ID: A6576178-2896-435C-9CD4-B71D849AA376@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 16 May 2024, at 15:54, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Wed, May 15, 2024 at 9:33 AM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> Ok, yeah, I can see that now. Here's a new version to address that. I
>> merged ENC_SSL_NEGOTIATED_SSL and ENC_SSL_DIRECT_SSL to a single method,
>> ENC_SSL. The places that need to distinguish between them now check
>> conn-sslnegotiation. That seems more clear now that there is no fallback.
>
> Unless there is a compelling reason to do otherwise, we should
> expedite getting this committed so that it is included in beta1.
> Release freeze begins Saturday.

+1. Having reread the thread and patch I think we should go for this one.

./daniel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-05-16 14:15:09 avoid MERGE_ACTION keyword?
Previous Message Joe Conway 2024-05-16 14:04:02 Re: PostgreSQL 17 Beta 1 release announcement draft