| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, 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> |
| Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: SSL/TLS instead of SSL in docs |
| Date: | 2021-06-30 18:20:50 |
| Message-ID: | 0f69b58e-e9da-3d03-d83d-94d7c935b993@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15.06.21 15:59, Daniel Gustafsson wrote:
> Looking at the docs it turns out that we have a mix of SSL (with one ssl),
> SSL/TLS and TLS for referring to the same thing. The attached changes the
> documentation to consistently use SSL/TLS when referring to an encrypted
> connection using a TLS protocol, leaving bare SSL and TLS only for referring to
> the actual protocols. I*think* I found all instances, there are many so I
> might have missed some, but this version seemed like a good place to continue
> the discussion from the previous thread.
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. If we are
not, then saying SSL is enough.
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. curl is a bit more inconsistent but also
generally just uses SSL. So it seems not a lot of people are really
bothered by this.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2021-06-30 18:43:09 | Re: SSL/TLS instead of SSL in docs |
| Previous Message | Peter Geoghegan | 2021-06-30 17:43:24 | Re: What is "wraparound failure", really? |