Re: Direct SSL connection and ALPN loose ends
| От | Jacob Champion |
|---|---|
| Тема | Re: Direct SSL connection and ALPN loose ends |
| Дата | |
| Msg-id | CAOYmi+=YCdJVAqbCYJy60Nc2PARvNncm6SaBnhaJiJy2xncjMg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Direct SSL connection and ALPN loose ends (Jacob Champion <jacob.champion@enterprisedb.com>) |
| Ответы |
Re: Direct SSL connection and ALPN loose ends
|
| Список | 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 по дате отправления: