Bug 57460 - HTTPS confusion between www.libreoffice.org and www.documentfoundation.orgh
Summary: HTTPS confusion between www.libreoffice.org and www.documentfoundation.orgh
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: WWW (show other bugs)
(earliest affected)
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL: https://www.libreoffice.org/get-help/...
Depends on:
Reported: 2012-11-23 15:37 UTC by Lionel Elie Mamane
Modified: 2012-11-24 00:22 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description Lionel Elie Mamane 2012-11-23 15:37:08 UTC
The #libreoffice-dev IRC channel has in its topic:
  bugs: http://goo.gl/IM1Yw

Which redirects to https://www.libreoffice.org/get-help/bug/, but then my browser gives me security alerts that www.libreoffice.org returned security information for www.documentfoundation.org
Comment 1 Korrawit Pruegsanusak 2012-11-23 16:13:28 UTC
What's your browser and version, please?

Sounds like:
* http://nabble.documentfoundation.org/SSL-Problem-td3696325.html
* http://nabble.documentfoundation.org/libreoffice-org-uses-an-invalid-security-certificate-td3243656.html -- please see Florian's answer
Comment 2 Lionel Elie Mamane 2012-11-23 17:14:56 UTC
(In reply to comment #1)
> What's your browser and version, please?

Galeon 2.0.7; based on Mozilla code; Debian package 2.0.7-2.1+b1

I'd expect SNI support comes from the underlying Mozilla code, but not 100% sure.
Comment 3 Christian Lohmaier 2012-11-23 19:34:40 UTC
Well, nothing that can be fixed - if SNI doesn't work reliably in the broser, then you have to live with the warnings.

IPv4 addresses are all assigned, so we have to use the same address for a couple of domains.

As the problem is not fixable, due to the nature of it, and since only old browser are affected → worksforme.
Comment 4 Lionel Elie Mamane 2012-11-24 00:22:40 UTC
https://sni.velox.ch/ says my browser sends TLS SNI extension in its ClientHello.

And now, I can't reproduce the issue from same computer, same browser. So must have been a transient server issue :)