Request a Demo
Home   >   mailing lists

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

From Vladimir Sitnikov
Subject Re: Direct SSL connection and ALPN loose ends
Date
Msg-id CAB=Je-G2PK94s_N7Pd6zRO8pYZ1NAnvJg=L2XQgKg9-eTLSvsA@mail.gmail.com
Whole thread
In response to Re: Direct SSL connection and ALPN loose ends  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: Direct SSL connection and ALPN loose ends
List pgsql-hackers
Tree view
I reviewed the documentation for "direct ALPN connections' ', and it looks like it could be improved.

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?

"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.

Vladimir

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pg_combinebackup --clone doesn't work
Next
From: Aleksander Alekseev
Date:
Subject: Re: PostgreSQL does not compile on macOS SDK 15.0