| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Jacob Champion <jchampion(at)timescale(dot)com>, heath(dot)lord(at)crunchydata(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17625: In PG15 PQsslAttribute returns different values than PG14 when SSL is not in use for the connection |
| Date: | 2022-09-29 21:37:15 |
| Message-ID: | 8F5DD45F-8A0D-4CBE-93B9-844C55886B85@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 29 Sep 2022, at 23:08, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> A definition that'd be consistent with what we just agreed to for
> PQsslAttribute is:
>
> PQsslAttributeNames(NULL): the attributes for the default SSL library,
> or an empty list if there is none.
>
> PQsslAttributeNames(conn): the attributes for the SSL library in use
> on this connection, or an empty list if not encrypted.
I think that makes sense, it keeps the API consistent.
> This doesn't cover how to find out the attributes for a non-default
> SSL library in advance of using it, but since PQsslAttribute would
> also need extension for multiple libraries, we could leave that
> for later.
Agreed, let's leave that for later.
--
Daniel Gustafsson https://vmware.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-29 21:58:11 | Re: BUG #17625: In PG15 PQsslAttribute returns different values than PG14 when SSL is not in use for the connection |
| Previous Message | Tom Lane | 2022-09-29 21:29:14 | Re: BUG #17625: In PG15 PQsslAttribute returns different values than PG14 when SSL is not in use for the connection |