| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
| Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: Support for NSS as a libpq TLS backend |
| Date: | 2020-07-15 22:18:26 |
| Message-ID: | 08B1D888-6151-4002-B0C2-488893AB51B2@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 15 Jul 2020, at 20:35, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> wrote:
>
> On 5/15/20 4:46 PM, Daniel Gustafsson wrote:
>>
>> My plan is to keep hacking at this to have it reviewable for the 14 cycle, so
>> if anyone has an interest in NSS, then I would love to hear feedback on how it
>> works (and doesn't work).
>
> I'll be happy to help, particularly with Windows support and with some
> of the callback stuff I've had a hand in.
That would be fantastic, thanks! The password callback handling is still a
TODO so feel free to take a stab at that since you have a lot of context on
there.
For Windows, I've include USE_NSS in Solution.pm as Thomas pointed out in this
thread, but that was done blind as I've done no testing on Windows yet.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-07-15 22:48:28 | sys_siglist[] is causing us trouble again |
| Previous Message | Daniel Gustafsson | 2020-07-15 22:16:26 | Re: Support for NSS as a libpq TLS backend |