Hello Damjan, all, On Tue, Apr 26, 2022 at 07:56:22PM +0200, Damjan Jovanovic wrote:
> On Mon, Nov 15, 2021 at 9:57 PM Jim Jagielski <j...@jagunet.com> wrote: > > > I'm gonna look into the serf->(lib)curl option... Since we don't use any > > of the fancy features of serf, I'm thinking that the easy option might be > > best > > > > Hi > > I've ported our WebDAV content provider module from Serf to Curl. I just enhanced the error reporting a bit; I am finding a problem under Linux and I do not really know how to assess it. The problem: if we build AOO on CentOS (that is our reference platform) then Curl will look for CA certificates in /etc/pki/tls/certs/ca-bundle.crt This will fail on openSUSE and probably on Ubuntu as well. It seems that the above path is set at configure time and embedded into Curl's code as #define macros. Is there an ``official'' way to assess this? Like, can we depend on NSS' certificate store as you wrote (quoted below)? [...] > HTTPS works, with a custom certificate verification function, using our own > certificate store from NSS and its API (like the Serf code used). A bug was > discovered (which is in the Serf implementation too) where self-signed > certificates were being unconditionally rejected; apparently NSS wants to > see that a copy of that certificate in its certificate chain parameter > too. Now they work, and the user gets prompted to allow access. Thank you in advance and best regards, -- Arrigo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
