Re: SSL/TLS instead of SSL in docs
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Bruce Momjian <bruce@momjian.us>, Tom Lane <tgl@sss.pgh.pa.us>, Magnus Hagander <magnus@hagander.net>, Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, Jeff Davis <pgsql@j-davis.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-25T02:45:44Z
Lists: pgsql-hackers
On Thu, Jun 24, 2021 at 01:53:47PM +0200, Daniel Gustafsson wrote: > The attached v3 does it this way. Thanks. Mostly what was on message upthread. Applied this one. > Yes, there are a few but not too many. Whenever the protocol is refererred to > and not the concept of an encrypted connection, just the applicable term is > used. Makes sense. > The attached v3 wraps SSL/TLS in a single acronym block, which for sure is more > pleasing to the eye when working with the docs, but I still have no idea which > version technically is the most correct. I am not sure 100% sure, but I would still vote in favor of this change, perhaps with a small addition of one extra entry for SSL/TLS directly on the acronym's page for consistency. What you have here sounds rather fine to me. > It doesn't, I'm just not convinced that the acronyms page is consulted all too > frequently anymore to provide much value. I might be totally wrong though. > Either way, thats (potentially) for a separate discussion. No idea about that. -- Michael
Commits
-
doc: Clarify when SSL actually means TLS
- 860ea46ba7be 15.0 landed
-
doc: Add acronyms for MITM and SNI
- 15ff5401d171 14.0 landed
-
doc: Apply markup <productname> to OpenSSL more consistently
- f80979f659d3 14.0 landed
-
Introduce --with-ssl={openssl} as a configure option
- fe61df7f82aa 14.0 cited