Re: SSL/TLS instead of SSL in docs
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
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-30T20:46:37Z
Lists: pgsql-hackers
> On 30 Jun 2021, at 20:20, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote: > I am not in favor of this direction. I think it just adds tediousness and doesn't really help anyone. If we are worried about correct terminology, then we should just change everything to TLS. I actually think SSL/TLS has won the debate of "correct terminology" for describing a secure connection encrypted by a TLS protocol. > If we are not, then saying SSL is enough. I think consistency is the interesting aspect here. We already have a mix of SSL, TLS and SSL/TLS (although heavily skewed towards SSL) so we should settle on one and stick to it. The arguments in the NSS thread which led to this pointed to SSL/TLS. If we feel that the churn isn't worth it, then we should change all to SSL and perhaps instead just add TLS as indexterms to those sections. -- Daniel Gustafsson https://vmware.com/
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