Horton

Re: SSL/TLS instead of SSL in docs

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

View thread View on postgr.es
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Jacob Champion <pchampion@vmware.com>, "daniel@yesql.se" <daniel@yesql.se>, "bruce@momjian.us" <bruce@momjian.us>, "magnus@hagander.net" <magnus@hagander.net>, "andrew.dunstan@2ndquadrant.com" <andrew.dunstan@2ndquadrant.com>, "tgl@sss.pgh.pa.us" <tgl@sss.pgh.pa.us>, "pgsql@j-davis.com" <pgsql@j-davis.com>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2021-07-01T20:26:55Z
Lists: pgsql-hackers 
On 30.06.21 20:43, Jacob Champion wrote:
> On Wed, 2021-06-30 at 20:20 +0200, Peter Eisentraut wrote:
>> I note that popular places such as the Apache and nginx SSL/TLS modules
>> just use SSL in their documentation, and they are probably under much
>> more scrutiny in this area.
> 
> For Apache, that's not strictly true [1, 2]. mod_ssl and its directive
> names are probably a lost cause due to inertia, but the page titles
> themselves have mostly changed to SSL/TLS.

> [1] https://httpd.apache.org/docs/2.4/ssl/
> [2] https://httpd.apache.org/docs/2.4/ssl/ssl_intro.html

That page entirely supports my point: It uses "SSL" throughout, except 
in the title and where it talks about the specific protocol names.

Commits

  1. doc: Clarify when SSL actually means TLS

  2. doc: Add acronyms for MITM and SNI

  3. doc: Apply markup <productname> to OpenSSL more consistently

  4. Introduce --with-ssl={openssl} as a configure option