:TLS_AES_128_GCM_SHA256" as
ciphers for TLS1.3 connection?
Thanks,
Erica Zhang
Original Email
Sender:"Jelte Fennema-Nio"< postg...@jeltef.nl ;
Sent Time:2024/6/12 16:51
To:"Erica Zhang"&l
instead.
Original Email
Sender:"Jelte Fennema-Nio"< postg...@jeltef.nl ;
Sent Time:2024/6/12 16:51
To:"Daniel Gustafsson"< dan...@yesql.se ;
Cc recipient:"Erica Zhang"<
Sender:"Michael Paquier"< mich...@paquier.xyz ;
Sent Time:2024/6/7 18:46
To:"Erica Zhang"< ericazhangy2...@qq.com ;
Cc recipient:"Peter Eisentraut"< pe...@eisentraut.org ;"pgsql-hackers"<
pgsql-hackers@lists.postgresql.org ;
Subject:Re: Re: A
accodingly.
Original Email
Sender:"Peter Eisentraut"< pe...@eisentraut.org ;
Sent Time:2024/6/7 16:55
To:"Erica Zhang"< ericazhangy2...@qq.com ;"pgsql-hackers"<
pgsql-hackers@lists.postgresql.org ;
Subject:Re: Add
Hi All,
I’m a Postgres user and I’m looking into restricting the set of allowed ciphers
on Postgres and configure a concrete set of curves on our postgres instances.
I see in current Postgres doc mentioned that only TLS1.2 and below cipher lists
can be configured. And there is no setting that
Hi Julien,
--Original--
From:
"Julien Rouhaud"
Hi Julien,
Thanks a lot for the quick review. Please see my answer below in blue. Attached
is the new patch.
-- Original --
From:
"Julien
Hi All,
On the master branch, it is possible to install multiple versions of
pg_stat_statements with CREATE EXTENSION, but all the tests in sql/ on look at
the latest version available, without testing past compatibility.
Since we support to install lowest version 1.4 currently, add some tests
