Re: SSL/TLS instead of SSL in docs

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: SSL/TLS instead of SSL in docs
Date: 2021-07-01 20:40:25
Message-ID: ab56060e-f49b-2db2-0734-156f48c25a41@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 30.06.21 22:46, Daniel Gustafsson wrote:
> 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.

I think it is already consistent in that it uses "SSL". Is that not the
case?

I notice that the NSS documentation also uses "SSL" almost exclusively
when referring to the SSL and TLS protocols and related APIs.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2021-07-01 21:08:50 Re: make world and install-world without docs
Previous Message Fabien COELHO 2021-07-01 20:36:08 Re: rand48 replacement