Re: Direct SSL connection and ALPN loose ends - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Direct SSL connection and ALPN loose ends
Date
Msg-id CAOYmi+=YCdJVAqbCYJy60Nc2PARvNncm6SaBnhaJiJy2xncjMg@mail.gmail.com
Whole thread Raw
In response to Re: Direct SSL connection and ALPN loose ends  (Jacob Champion <jacob.champion@enterprisedb.com>)
Responses Re: Direct SSL connection and ALPN loose ends
List pgsql-hackers
On Mon, Jun 17, 2024 at 9:23 AM Jacob Champion
<jacob.champion@enterprisedb.com> wrote:
> > I think the behavior with v2 and v3 errors should be the same. And I
> > think an immediate failure is appropriate on any v2/v3 error during
> > negotiation, assuming we don't use those errors for things like "TLS not
> > supported", which would warrant a fallback.
>
> For GSS encryption, it was my vague understanding that older servers
> respond with an error rather than the "not supported" indication. For
> TLS, though, the decision in a49fbaaf (immediate failure) seemed
> reasonable.

Would an open item for this be appropriate?

Thanks,
--Jacob



pgsql-hackers by date:

Previous
From: "David E. Wheeler"
Date:
Subject: Re: Extension security improvement: Add support for extensions with an owned schema
Next
From: Robert Haas
Date:
Subject: call for applications: mentoring program for code contributors