Hi,

Am 23.08.20 um 01:51 schrieb Dave Fisher:
> Hi -
>
> This is excellent. I’ve been investigating the code.

My Windows Test builds are up (incl. openSSL1.0.2t):

https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/

>
> The services are called from main/extensions/source/update/check/download.cxx 
> using Curl.
>
> To fully confirm the fix the next step is to check into curl dependencies:
>
> https://curl.haxx.se/docs/libs.html
>
> OpenSSL is one of Curl’s TLS providers.
>
> Judging from the config.log files from past releases in 
> https://svn.apache.org/viewvc/openoffice/devtools/build-scripts/ which only 
> go back to 4.1.2.
>
> (1) Mac versions of AOO since 4.1.2 are built using the SYSTEM_OPENSSL=“YES” 
> which should explain why we are getting update checks from many or most of 
> our user’s Mac installations.
>
> (2) Our released versions of Linux and Windows have SYSTEM_OPENSSL=“NO”. It 
> could be that the handful of versions that do work were compiled from source 
> with SYSTEM_OPENSSL=“YES”.
>
> Does this make sense?

I am not sure, Windows has no SYSTEM_OPENSSL. Of course people could
have edited the URL but why would they stay on an old version then?

I had one week when AOO on Ubuntu could connect to the server, then it
broke again. Something changed on the way from my computer to the update
feed...

Regards,

   Matthias

>
> Regards,
> Dave
>
>> On Aug 22, 2020, at 3:32 PM, Don Lewis <[email protected]> wrote:
>>
>> On 23 Aug, Matthias Seidel wrote:
>>> Hi Don,
>>>
>>> Finished my Windows builds and AOO 4.1.8 can connect to both, AOO
>>> updates and Extension updates.
>> Cool.  I'll go ahead and merge the pull request.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to