Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
Subject: Re: Support for NSS as a libpq TLS backend
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <b6bd9ad9-f8d2-3445-94b4-574e39cdfee2@2ndQuadrant.com>
Date: Thu, 16 Jul 2020 00:18:26 +0200
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>,
 Stephen Frost <sfrost@snowman.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08B1D888-6151-4002-B0C2-488893AB51B2@yesql.se>
References: <FAB21FC8-0F62-434F-AA78-6BD9336D630A@yesql.se>
 <b6bd9ad9-f8d2-3445-94b4-574e39cdfee2@2ndQuadrant.com>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Precedence: bulk

> On 15 Jul 2020, at 20:35, Andrew Dunstan =
<andrew.dunstan@2ndquadrant.com> wrote:
>=20
> On 5/15/20 4:46 PM, Daniel Gustafsson wrote:
>>=20
>> 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).
>=20
> 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=