Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)
Replying to myself again... On Sat, Apr 30, 2022 at 10:03:54PM +0200, Arrigo Marchiori wrote: > Replying to myself... > > On Sat, Apr 30, 2022 at 09:41:04PM +0200, Arrigo Marchiori wrote: > > > Hello Damjan, > > > > On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote: > [...] > > > When I run your Linux binaries, I also get that error. > > > > > > One problem is libcurl -> openssl. > > > > > > "ldd ./libcurl.so" shows: > > > libssl.so.10 => not found > > > libcrypto.so.10 => not found > [...] > > > > > > It connects and seems to begin the SSL negotiations, and then probably > > > crashes while doing the verify_callback we set with SSL_CTX_set_verify(). > > > > > > I suspect the Curl and/or OpenSSL headers used to build AOO, and their > > > libraries available at runtime, are incompatible. > > > > > > What happens if you run AOO on the same machine it was built on? > [...] > > As I wrote above, according to your suspects, it may be worthwile to > > bundle curl and openssl binaries. I will try to follow this path. It > > should be a matter of parameters to the configure script. > > Curl and openssl are already bundled. > > But Curl is not using the openssl from AOO, but rather from the > system. In other words, it does not honor the environment variable > SYSTEM_OPENSSL=NO set by the AOO build system. > > Curl's configure script looks for the SSL headers and libraries either > from pkgconfig or at a path provided with parameter --with-ssl > > We do not support pkgconfig inside the solver, so we have to rely on > the path. > > But Curl's configure script expects to find a directory structure such as: > - $PREFIX/include/openssl > - $PREFIX/lib[64] > whereas our $OUTDIR has openssl installed into different paths: > - $OUTDIR/inc/external/openssl > - $OUTDIR/lib > > I believe this means we have to patch Curl's configure script. Not only. We also have to actually bundle libssl.so and libcrypto.so because they are not! This means we have to patch: - main/openssl/prj/d.lst to have them included into the solver; - scp2/source/ooo/file_library_ooo.scp to have their Unix names included. This is a separate bug and will be worth its own pull request. Comments are welcome. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)
Replying to myself... On Sat, Apr 30, 2022 at 09:41:04PM +0200, Arrigo Marchiori wrote: > Hello Damjan, > > On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote: [...] > > When I run your Linux binaries, I also get that error. > > > > One problem is libcurl -> openssl. > > > > "ldd ./libcurl.so" shows: > > libssl.so.10 => not found > > libcrypto.so.10 => not found [...] > > > > It connects and seems to begin the SSL negotiations, and then probably > > crashes while doing the verify_callback we set with SSL_CTX_set_verify(). > > > > I suspect the Curl and/or OpenSSL headers used to build AOO, and their > > libraries available at runtime, are incompatible. > > > > What happens if you run AOO on the same machine it was built on? [...] > As I wrote above, according to your suspects, it may be worthwile to > bundle curl and openssl binaries. I will try to follow this path. It > should be a matter of parameters to the configure script. Curl and openssl are already bundled. But Curl is not using the openssl from AOO, but rather from the system. In other words, it does not honor the environment variable SYSTEM_OPENSSL=NO set by the AOO build system. Curl's configure script looks for the SSL headers and libraries either from pkgconfig or at a path provided with parameter --with-ssl We do not support pkgconfig inside the solver, so we have to rely on the path. But Curl's configure script expects to find a directory structure such as: - $PREFIX/include/openssl - $PREFIX/lib[64] whereas our $OUTDIR has openssl installed into different paths: - $OUTDIR/inc/external/openssl - $OUTDIR/lib I believe this means we have to patch Curl's configure script. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: WebDAV module ported from serf to curl; curl using openssl and zlib (was: Re: Openssl, serf and curl)
Hello Damjan,
On Fri, Apr 29, 2022 at 04:53:59AM +0200, Damjan Jovanovic wrote:
> On Thu, Apr 28, 2022 at 8:46 PM Arrigo Marchiori
> wrote:
>
> > Hello Damjan,
> >
> > On Thu, Apr 28, 2022 at 06:53:43PM +0200, Damjan Jovanovic wrote:
> >
> > > On Thu, Apr 28, 2022 at 6:12 PM Arrigo Marchiori > >
> > > wrote:
> > >
> > > > Dear 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
> > 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.
> > > >
> > > > Binary for Linux available here for download:
> > > >
> > > >
> > https://home.apache.org/~ardovm/openoffice/linux/openoffice4-serf2curl-2022-04-28-installed.tar.bz2
> > > >
> > > > I understand from your previous message that you don't really like
> > > > GitHub, so I am writing here.
> > > >
> > > > [...]
> > > > > STATUS
> > > > >
> > > > > It builds and works well on FreeBSD and Windows.
> > > > >
> > > > > Most of the code was reused, and all the operations and semantics
> > > > > previously present with Serf, should have been preserved.
> > > > >
> > > > > Browsing WebDAV files and directories, loading files, overwriting
> > them
> > > > > ("Save"), creating them ("Save As"), renaming and deleting them, all
> > > > works.
> > > >
> > > > I am testing the binary for Linux linked above.
> > > >
> > > > I tried "Open" and entered a https address, that I know is password
> > > > protected.
> > > >
> > > > The current trunk would ask for the password. I got an error message
> > > > instead:
> > > >
> > > > > > Nonexistent object.
> > > > > > Nonexistent file.
> > > >
> > > > The address I tried to open is in the form https://host.domain:port/
> > > >
> > > > I tried to substitute "https" with "davs" and I got the same error.
> > > >
> > > > Maybe something is going wrong in the Linux build?
> > > >
> > > > I will now begin recompiling with debugging symbols enabled. Please
> > > > let me know how I can help.
> > > >
> > >
> > > That's not good :(.
> > >
> > > Set your macro security to "Medium", open the spreadsheet I've attached,
> > > and run the "RunMe" Basic macro. That should enable logging to the
> > console
> > > at the finest level of detail. Then exit and re-run AOO like this:
> > > soffice 2>&1 | tee /tmp/log.txt
> > > and examine the console output interactively as you use AOO, and/or check
> > > the log file afterwards. It should have everything, our logging, HTTP
> > > request and response headers and bodies, Curl's internal logging.
> >
> > I can't get to that point.
> >
> > I fired gdb and it seems that I end up into the blind
> > catch (Exception const &)
> > block in file ucb/source/core/provprox.cxx:361
> >
> > Method UcbContentProviderProxy::getContentProvider() in fact is called
> > many times, but it only fails when I enter the https url in the "Open"
> > dialog box and press ENTER.
> >
> > Sorry this is all the debugging I can do for today. I hope it helps.
> >
> >
> When I run your Linux binaries, I also get that error.
>
> One problem is libcurl -> openssl.
>
> "ldd ./libcurl.so" shows:
> libssl.so.10 => not found
> libcrypto.so.10 => not found
This probably means that we have to ship our own binaries of openssl
on Linux.
> When I rename AOO's libcurl.so so that it's forced to use my system libcurl
> instead, it proceeds further, but runs into another problem:
>
> Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
> 0x0001 in ?? ()
[...snip of stack trace with no debugging symbols...]
>
> It gets far enough to log and produces some output before the crash:
>
> 11 2022-04-29 02:24:24.03 CurlSession::CurlSession with
> URL https://10.0.2.2:82/files/
> 21 2022-04-29 02:24:24.03 Not using a proxy server
> 31 2022-04-29 02:24:24.03 PROPFIND line 914
> 41 2022-04-29 02:24:24.03 [CurlINFO ] Trying 10.0.2.2:82
> ...
> 51 2022-04-29 02:24:24.03 [CurlINFO ] TCP_NODELAY set
> 61 2022-04-29 02:24:24.03 [CurlINFO ] Connected to
> 10.0.2.2 (10.0.2.2) port 82 (#0)
> 71 2022-04-29 02:24:24.03 [CurlINFO ] ALPN, offering h2
> 81 2022-04-29 02:24:24.03 [CurlINFO ] ALPN, offering
> http/1.1
> 91 2022-04-29 02:24:24.04 [CurlINFO ] successfully set
> certificate verify locations:
> 101 2022-04-29 02:24:24.04 [CurlINFO ] CAfile:
> /etc/ssl/certs/ca-certificates.crt
> CApath: /etc/ssl/certs
>
> It connects and seems to begin the SSL negotiations, and then probably
> crashes while doing the verify_callback we set with
Re: [CLOSED] [VOTE] Release AOO 4.1.12-RC1 as GA
Hi Jim, SourceForge is a bit slow this time, but at the moment all the binaries I checked are available on 8 mirrors. I think that is a good base. Regards, Matthias Am 27.04.22 um 14:21 schrieb Jim Jagielski: > Cool. I'l copy over the rest of the build assets > >> On Apr 26, 2022, at 3:00 PM, Matthias Seidel >> wrote: >> >> Hi Jim, >> >> Signed Windows binaries are uploaded now. >> >> Regards, >> >>Matthias >> >> Am 26.04.22 um 16:01 schrieb Matthias Seidel: >>> Hi Jim, >>> >>> Am 26.04.22 um 15:24 schrieb Jim Jagielski: I was hoping for more testing and feedback, but we have rec'd the necessary number of binding votes, and so this VOTE PASSES. >>> Yes, I also hoped for more... >>> >>> However, I will start to sign the Windows binaries and upload them later >>> to dist/dev. >>> >>> Regards, >>> >>>Matthias >>> > On Apr 13, 2022, at 9:54 AM, Jim Jagielski wrote: > > I am calling a VOTE on releasing the source and complimentary community > builds of > Apache OpenOffice 4.1.12-RC1 as GA. > > These artifacts can be found at: > > https://dist.apache.org/repos/dist/dev/openoffice/4.1.12-RC1/ > > Please cast your vote: > > The Release Candidate is good for production/GA: > > [ ] yes / +1 > > [ ] no / -1 > > My vote is based on > > [ ] binding (member of PMC) > > [ ] I have built and tested the RC from source on platform [ ] > > [ ] I have tested the binary RC on platform [ ] > > This vote will be open for 7 days to allow for sufficient time > for testing, review, and voting. > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > smime.p7s Description: S/MIME Cryptographic Signature
