Pedro Lino wrote:>> On November 19, 2018 at 12:52 AM Branko Čibej wrote:
It looks like you found the real problem:
$ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/
This makes sense, but I still don't understand it as the full explanation.
I mean, if this is due to bundled libraries then why do the same
binaries produce different results on different systems?
This is config.log from my test 4.1.6 build (done on CentOS 7):
---
configure:16978: checking which libnss to use
configure:17076: result: internal
configure:17088: checking which libssl to use
configure:17194: result: internal
---
so this should mean we are using bundled libraries.
Then I copy the produced binaries to Ubuntu 16.04 and to Fedora 26
(these happen to be the machines that I setup for this test).
On CentOS 7 (where it was built):
$ ./soffice https://ooo-updates.apache.org/index.html # Fails
$ ./soffice https://fosdem.org # Succeeds
$ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/ # Fails
On Ubuntu 16.04:
$ ./soffice https://ooo-updates.apache.org/index.html # Fails
$ ./soffice https://fosdem.org # Succeeds
$ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/ # Fails
On Fedora 26:
$ ./soffice https://ooo-updates.apache.org/index.html # Succeeds!
$ ./soffice https://fosdem.org # Succeeds
$ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/ # Fails
Does the current explanation actually explain why the first command
succeeds on Fedora? (of course, this also reflects in GUI, where the
check for updates only succeeds on Fedora).
Can this change be reversed or an exception opened for AOO?
Sure, we have multiple options available. Including moving this server
to a smaller (or even dedicated) virtual machine. Note that, even if we
miss a full explanation, we could still try this, but I'm really curious
to know whether the Fedora behavior can be explained.
how are users going to be notified that any future version is available?
Fortunately we can fix this in code, even though Brane explained well
why this is hard to do on the 4.1.x line.
@_Andreas_, which AOO version are you using under which OS?
The three above, plus the official 4.1.6 build on both Fedora 26 and a
new machine, Ubuntu 18.04 (with the usual results: Fedora succeeds,
Ubuntu fails).
I can confirm that version 4.2.0 build 1846852 does connect under Ubuntu 16.04.5
Yes, same for me on Ubuntu 16.04 with 4.2.0-dev (I get the same results
as on Fedora, and no errors if I check for updates).
The current explanation we have is very good.
I'm just left with the big question mark of why 4.1.6 works well in
Fedora and the same binaries fail on CentoOS 7 (where I built them) and
Ubuntu 16.04. If we could explain this last part we would be able to go
to Infra with more confidence.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
