| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ssl_library parameter |
| Date: | 2018-06-27 06:12:31 |
| Message-ID: | 0c9e8c80-ae4d-faab-c4a1-ddb15f50a9c9@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/26/18 17:48, Tom Lane wrote:
> (1) I'm not really clear why we need this. GUC variables aren't free.
>
> (2) Are there security issues with exposing this info to everybody?
This functionality was requested in the threads about GnuTLS and other
SSL implementations so that users/admins can determine which SSL
settings are applicable.
I'm not sure about the security impact. We do expose all the other
ssl_* settings to ordinary users, so if users want to see whether the
server is misconfigured or something like that, they can already do
that. I think in the context of an SSL connection, the server is not
supposed to be the adversary of the client, so if the server can provide
more information about what it's doing to protect the client's
information, then the better.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Chalke | 2018-06-27 06:13:59 | Re: Server crashed with TRAP: FailedAssertion("!(parallel_workers > 0)" when partitionwise_aggregate true. |
| Previous Message | Amit Langote | 2018-06-27 06:03:54 | Re: partitioning - changing a slot's descriptor is expensive |