From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 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>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
Subject: | Re: SSL/TLS instead of SSL in docs |
Date: | 2022-03-25 21:01:01 |
Message-ID: | 4A1542D5-740F-425B-A96B-20A98F404063@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 25 Mar 2022, at 20:58, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Wed, Sep 15, 2021 at 8:47 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>> Since the approach taken wasn't to anyones liking, attached is a v4 (partly
>> extracted from the previous patch) which only adds notes that SSL is used
>> interchangeably with TLS in our documentation and configuration.
>
> I have actually been wondering why we have been insisting on calling
> it SSL when it clearly is not.
SSL has become the de facto term for a network channel encryption regardless of
actual protocol used. Few use TLS, with most SSL/TLS is
> 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.
--
Daniel Gustafsson https://vmware.com/
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-03-25 21:02:02 | Re: Document atthasmissing default optimization avoids verification table scan |
Previous Message | Tom Lane | 2022-03-25 21:00:43 | Re: Document atthasmissing default optimization avoids verification table scan |