On Wed, 12 Jun 2024 at 04:32, Erica Zhang <ericazhangy2...@qq.com> wrote: > There are certain government, financial and other enterprise organizations > that have very strict requirements about the encrypted communication and more > specifically about fine grained params like the TLS ciphers and curves that > they use. The default ones for those customers are not acceptable. Any > products that integrate Postgres and requires encrypted communication with > the Postgres would have to fulfil those requirements.
Yeah, I ran into such requirements before too. So I do think it makes sense to have such a feature in Postgres. > So if we can have this patch in the upcoming new major version, that means > Postgres users who have similar requirements can upgrade to PG17. As Daniel mentioned you can already achieve the same using the "Ciphersuites" directive in openssl.conf. Also you could of course always disable TLSv1.3 support.
