| From: | Dave Cramer <davecramer(at)postgres(dot)rocks> |
|---|---|
| To: | Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Direct SSL connection and ALPN loose ends |
| Date: | 2024-06-25 14:20:30 |
| Message-ID: | CADK3HH+cxnjLSj0o6kHWXF05ARpd3ZM2Oufhp4OYVJJjBwZ=kw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 25 Jun 2024 at 09:37, Vladimir Sitnikov <sitnikov(dot)vladimir(at)gmail(dot)com>
wrote:
> I reviewed the documentation for "direct ALPN connections' ', and it looks
> like it could be improved.
> Here's the link:
> https://www.postgresql.org/docs/17/protocol-flow.html#PROTOCOL-FLOW-SSL
>
> The currently suggested values for "sslnegotiations" are "direct" and
> "postgres".
> The project name is PostgreSQL and the ALPN name is postgresql. Is there a
> reason why property value uses "postgres"?
> Can the value be renamed to postgresql for consistency?
>
+1 I found it strange that we are not using postgresql
>
> "SSL". Technically, the proper term is TLS, and even the document refers
> to "IANA TLS ALPN Protocol IDs" (TLS, not SSL).
> I would not die on that hill, however, going for tlsnegotiation would look
> better than sslnegotiation.
>
+1 again, unusual to use SSL when this really is TLS.
Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-06-25 14:21:58 | Re: improve ssl error code, 2147483650 |
| Previous Message | Muhammad Ikram | 2024-06-25 14:15:39 | Re: Recommended books for admin |