From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Jacob Champion <pchampion(at)vmware(dot)com> |
Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Andres Freund <andres(at)anarazel(dot)de>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
Subject: | Re: Support for NSS as a libpq TLS backend |
Date: | 2020-11-10 22:28:14 |
Message-ID: | B506D54C-BBB5-49C0-BF9A-BACEFAD8520D@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 10 Nov 2020, at 21:11, Jacob Champion <pchampion(at)vmware(dot)com> wrote:
> On Nov 6, 2020, at 3:11 PM, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>> The attached switches to SSL_ConfigServerSessionIDCacheWithOpt
>> with which one can explicitly make the cache non-shared, which in turn backs
>> the mutexes with NSPR locks rather than the missing sem_init. Can you test
>> this version and see if that makes it work?
>
> Yep, I get much farther through the tests with that patch.
Great, thanks for confirming.
> I'm currently
> diving into another assertion failure during socket disconnection:
>
> Assertion failure: fd->secret == NULL, at prlayer.c:45
>
> cURL has some ominously vague references to this [1], though I'm not
> sure that we should work around it in the same way without knowing what
> the cause is...
Digging through the archives from when this landed in curl, the assertion
failure was never fully identified back then but happened spuriously. Which
version of NSPR is this happening with?
cheers ./daniel
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2020-11-10 23:08:48 | Re: cutting down the TODO list thread |
Previous Message | David Rowley | 2020-11-10 22:01:57 | Re: Reduce the number of special cases to build contrib modules on windows |