Re: Support for NSS as a libpq TLS backend - Mailing list pgsql-hackers

From Joshua Brindle
Subject Re: Support for NSS as a libpq TLS backend
Date
Msg-id CAGB+Vh6Ja46xMwgKMYehEc1vx+uRPMvnCRM2s-QeMjZLquEiXg@mail.gmail.com
Whole thread Raw
In response to Re: Support for NSS as a libpq TLS backend  (Joshua Brindle <joshua.brindle@crunchydata.com>)
Responses Re: Support for NSS as a libpq TLS backend
List pgsql-hackers
On Tue, Nov 16, 2021 at 9:45 AM Joshua Brindle
<joshua.brindle@crunchydata.com> wrote:
>
> On Mon, Nov 15, 2021 at 5:37 PM Joshua Brindle
> <joshua.brindle@crunchydata.com> wrote:
> >
> > On Mon, Nov 15, 2021 at 4:44 PM Daniel Gustafsson <daniel@yesql.se> wrote:
> > >
> > > > On 15 Nov 2021, at 20:51, Joshua Brindle <joshua.brindle@crunchydata.com> wrote:
> > >
> > > > Apologies for the delay, this didn't go to my inbox and I missed it on list.
> > > >
> > > > The bitcode generation is still broken, this time for nspr.h:
> > >
> > > Interesting, I am unable to replicate that in my tree but I'll investigate
> > > further tomorrow using your Dockerfile.  For the sake of testing, does
> > > compilation pass for you in the same place without using --with-llvm?
> > >
> >
> > Yes, it builds and check-world passes. I'll continue testing with this
> > build. Thank you.
>
> The previous Dockerfile had some issues due to a hasty port from RHEL
> to Fedora, attached is one that works with your patchset, llvm
> currently disabled, and the llvm deps removed.
>
> The service file is also attached since it's referenced in the
> Dockerfile and you'd have had to reproduce it.
>
> After building, run with:
> docker run --name pg-test -p 5432:5432 --cap-add=SYS_ADMIN -v
> /sys/fs/cgroup:/sys/fs/cgroup:ro -d <final docker hash>

I think there it a typo in the docs here that prevents them from
building (this diff seems to fix it):

diff --git a/doc/src/sgml/pgcrypto.sgml b/doc/src/sgml/pgcrypto.sgml
index 56b73e033c..844aa31e86 100644
--- a/doc/src/sgml/pgcrypto.sgml
+++ b/doc/src/sgml/pgcrypto.sgml
@@ -767,7 +767,7 @@ pgp_sym_encrypt(data, psw, 'compress-algo=1,
cipher-algo=aes256')
    <para>
     Which cipher algorithm to use.  <literal>cast5</literal> is only available
     if <productname>PostgreSQL</productname> was built with
-    <productname>OpenSSL</productame>.
+    <productname>OpenSSL</productname>.
    </para>
 <literallayout>
 Values: bf, aes128, aes192, aes256, 3des, cast5



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Fix headerscheck failure in replication/worker_internal.h
Next
From: Andres Freund
Date:
Subject: Re: RecoveryInProgress() has critical side effects