From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Jacob Champion <pchampion(at)vmware(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Post-CVE Wishlist |
Date: | 2021-11-23 22:02:12 |
Message-ID: | 62574.1637704932@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I am not persuaded by this argument. Suppose we added a server option
> like ssl_port which causes us to listen on an additional port and, on
> that port, everything, from the first byte on this connection, is
> encrypted using SSL.
Right, a separate port number (much akin to http 80 vs https 443) is
pretty much the only way this could be managed. That's messy enough
that I don't see anyone wanting to do it for purely-hypothetical
benefits. If we'd done it that way from the start, it'd be fine;
but there's way too much established practice now.
> Now that being said, https://www.openldap.org/faq/data/cache/605.html
> claims that ldaps (encrpyt from the first byte) is deprecated in favor
> of STARTTLS (encrypt by negotiation). It's interesting that Jacob is
> proposing to introduce as a new and better option the thing they've
> decided they don't like.
Indeed, that is interesting. I wonder if we can find the discussions
that led to that decision.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bossart, Nathan | 2021-11-23 22:13:14 | Re: Sequence's value can be rollback after a crashed recovery. |
Previous Message | Robert Haas | 2021-11-23 21:44:43 | Re: Post-CVE Wishlist |