Re: SSL/TLS instead of SSL in docs

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>
To: Robert Haas <robertmhaas@gmail.com>
Cc: PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, 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>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Date: 2022-03-28T21:51:30Z
Lists: pgsql-hackers
> On 25 Mar 2022, at 22:01, Daniel Gustafsson <daniel@yesql.se> wrote:
>> On 25 Mar 2022, at 20:58, Robert Haas <robertmhaas@gmail.com> wrote:

>> However, if we're not ready/willing to make a bigger change, then doing as you
>> have proposed here seems fine to me.
> 
> Thanks for review!  Trying out again just now the patch still applies (with
> some offsets) and builds.

Barring objections I will go ahead and push this for 15.  It's the minimal
change but it might still help someone new to PostgreSQL who gets confused on
the choice of naming/wording.

--
Daniel Gustafsson		https://vmware.com/




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