Re: Check for Updates broken?
On 18.11.2018 23:30, Don Lewis wrote: > On 17 Nov, Pedro Lino wrote: >>> On November 17, 2018 at 5:32 PM Andrea Pescetti wrote: >>> A nice additional benefit is that this gives us a simple way to >>> reproduce the bug, equivalent to the update notification. >>> >>> $ soffice https://ooo-updates.apache.org/index.html >>> (this fails on Ubuntu, succeeds on Fedora) >>> >>> Note that >>> >>> $ soffice https://www.google.com/ >>> will work in all cases (so this is not an HTTPS bug per se) and >>> >>> $ soffice http://ooo-updates.apache.org/index.html >>> will work in all cases (so this not a network issue but rather an SSL >>> issue). >>> >>> Now, debugging SSL issues is not easy, but can the people who don't get >>> updates at least confirm the three results above, i.e., that only the >>> first one fails? >> Confirmed that only the first one fails. >> I always get the message (even when it didn't fail to open the page) >> >> Gtk-Message: Failed to load module "overlay-scrollbar" >> >> ** (soffice:10458): WARNING **: Unknown type: GailWindow >> >>> Further tests show that problematic systems have issues with ASF sites >>> in HTTPS, like: >>> $ soffice https://www.apache.org/ # Fails >>> $ soffice http://www.apache.org/ # Succeeds >>> $ soffice https://www.openoffice.org/ # Fails >>> $ soffice http://www.openoffice.org/ # Succeeds >>> $ soffice https://... # Succeeds for any site I put there, except ASF >>> sites, but I'd love to see a non-ASF example of a failing HTTPS site. >> Confirmed. HTTPS links fail, HTTP succeed > The HTTPS links all work for me with the FreeBSD port of 4.1.6. One > difference is that the FreeBSD port uses the system OpenSSL, currently > 1.02p or newer. > > Does the Apache web server still support TLS version 1.0? The old > version of OpenSSL that we bundle with the Windows and Linux versions > doesn't support anything newer than that. It looks like you found the real problem: $ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/ * Trying 40.79.78.1... ... * TLSv1.0 (OUT), TLS handshake, Client hello (1): * TLSv1.0 (IN), TLS alert, Server hello (2): * error:1400442E:SSL routines:CONNECT_CR_SRVR_HELLO:tlsv1 alert protocol version Connection fails with options --tlsv1.0 and --tlsv1.1 but succeeds with --tlsv1.2. Which is in fact a good thing; TLSv1 and TLSv1.1 both have known security bugs. It is usually a bad idea to bundle OpenSSL instead of using the system-provided version; but if you do have to do that (e.g., on Windows, which doesn't have it, or macOS, which has an ancient version), at least use the latest 1.0.2 version, or even better, 1.1.0. -- Brane - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Program for Sandro
The appraisal of completing expectations is fulfilling and I find it fulfilling to appreciate a smile in the face of my colleagues, because attainment fulfills the will and cooperation fulfills the emotion. I feel that the installation of MediaWiki was successful, it was a bright sight of confirmation of the beauty that I expected from this software. Now I want to write the actual skin, I tell write because it seen that I will have to write the CSS of the new skin and it fulfils myself as a discovery. Maybe in the next week I complete the task. I would like to tell that the Wiki project is really engrossing me like a tender delight or an advance to congratulation, I really like to drive myself to do Wiki. Glad, Sandro Suzart De: sandro Enviado: domingo, 28 de outubro de 2018 22:38 Para: dev@openoffice.apache.org Assunto: Re: [Discussion] Program for Sandro Dear Andrea, I have found the Wiki's Skin fulfilling because of it's friendly form and I have found the PHP work fulfilling because of it's sympathetic way. The friendly form is an aspect of a sympathetic way of work and I find it fulfilling both the friendly and the sympathetic aspects of the task. How good did I feel the CSS work? Well, I feel it a secure task because now the remain thing is the creation of a database to use the Wiki's editor. The Wiki's editor is an involving application and it works well in my browser, it is certainly driving me to happiness. Glad, Sandro Suzart De: Andrea Pescetti Enviado: sábado, 13 de outubro de 2018 16:11 Para: dev@openoffice.apache.org Assunto: Re: [Discussion] Program for Sandro On 06/09/2018 Peter kovacs wrote: > Hi Andrea, > Can you specify at least one task? So Sandro can make a plan. It took a while, but here I am with a task. One of the many things that would be nice to have is a new skin (i.e., graphical theme) for our MWiki https://wiki.openoffice.org/wiki/Main_Page (which is also being moved to a new server, but this is irrelevant to this discussion). This requires some PHP and design capabilities, and a tutorial is available at https://www.mediawiki.org/wiki/Manual:Skinning_Part_1 and related pages. Sandro, can this work as a task for you? All you will need is a standard MediaWiki installation from https://www.mediawiki.org/wiki/Download (I recommend the "stable LTS" version, since that is the one we are going to settle on) and the tutorial above. If you would like to receive the current skin (I don't even know if it is a skin or just a set of CSS customizations) just ask and I can provide it; but honestly I would start from https://www.mediawiki.org/wiki/Category:All_skins then find one that you like and extend/customize it. The logo must be updated too and Matthias already sent the new one. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for Updates broken?
On 17 Nov, Pedro Lino wrote: >> On November 17, 2018 at 5:32 PM Andrea Pescetti wrote: > >> A nice additional benefit is that this gives us a simple way to >> reproduce the bug, equivalent to the update notification. >> >> $ soffice https://ooo-updates.apache.org/index.html >> (this fails on Ubuntu, succeeds on Fedora) >> >> Note that >> >> $ soffice https://www.google.com/ >> will work in all cases (so this is not an HTTPS bug per se) and >> >> $ soffice http://ooo-updates.apache.org/index.html >> will work in all cases (so this not a network issue but rather an SSL >> issue). >> >> Now, debugging SSL issues is not easy, but can the people who don't get >> updates at least confirm the three results above, i.e., that only the >> first one fails? > > Confirmed that only the first one fails. > I always get the message (even when it didn't fail to open the page) > > Gtk-Message: Failed to load module "overlay-scrollbar" > > ** (soffice:10458): WARNING **: Unknown type: GailWindow > >> Further tests show that problematic systems have issues with ASF sites >> in HTTPS, like: >> $ soffice https://www.apache.org/ # Fails >> $ soffice http://www.apache.org/ # Succeeds >> $ soffice https://www.openoffice.org/ # Fails >> $ soffice http://www.openoffice.org/ # Succeeds >> $ soffice https://... # Succeeds for any site I put there, except ASF >> sites, but I'd love to see a non-ASF example of a failing HTTPS site. > > Confirmed. HTTPS links fail, HTTP succeed The HTTPS links all work for me with the FreeBSD port of 4.1.6. One difference is that the FreeBSD port uses the system OpenSSL, currently 1.02p or newer. Does the Apache web server still support TLS version 1.0? The old version of OpenSSL that we bundle with the Windows and Linux versions doesn't support anything newer than that. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Fwd: [ANNOUNCE] Apache OpenOffice 4.1.6 released
Hello OpenOffice community, today we want to share with you the announcement from below. Thank You to all who have helped, tested, hacked, discussed or were otherwise involved and have invested many hours of their spare time. Marcus (on behalf of the Apache OpenOffice PMC) Weitergeleitete Nachricht Betreff: [ANNOUNCE] Apache OpenOffice 4.1.6 released Datum: Sun, 18 Nov 2018 22:17:45 +0100 Von: Marcus Antwort an: annou...@openoffice.apache.org An: annou...@openoffice.apache.org 18 November 2018 - Apache OpenOffice, the leading Open Source office document productivity suite, announced today Apache OpenOffice 4.1.6, now available in 41 languages on Windows, macOS and Linux. Apache OpenOffice 4.1.6 is a maintenance release aimed at correcting some regressions and delivering the latest English dictionary. All users of Apache OpenOffice 4.1.5 or earlier are advised to upgrade. The main changes include: * Bug fixes * Updates for the English language dictionaries For the complete overview see the list in Bugzilla: https://s.apache.org/AOO-416changes Full version of this announcement: https://s.apache.org/AOO-416announcement Apache OpenOffice 4.1.6 Release Notes: https://s.apache.org/AOO-416releasenotes Download Apache OpenOffice 4.1.6 from the original source only: https://www.openoffice.org/download/ Follow Apache OpenOffice: Twitter https://twitter.com/apacheoo Facebook https://www.facebook.com/ApacheOO Google+ https://plus.google.com/u/0/+openoffice YouTube https://www.youtube.com/c/openoffice Mail https://openoffice.apache.org/mailing-lists.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for Updates broken?
On 18.11.2018 18:41, Branko Čibej wrote: > On 18.11.2018 17:19, Andrea Pescetti wrote: >> Pedro Lino wrote: >>> However the AOO site does not specify any charset. Could that be the >>> problem? >> I don't think the charset is a major issue, but indeed (if I do the >> same test with openssl) there is something interesting that can >> probably be submitted to Infra for investigation. >> >> On any system I've tried with (CentOS, Ubuntu, Fedora) >> >> $ openssl s_client -state -nbio -connect ooo-updates.apache.org:443 >> >> will show (in a lengthy output that I don't have the time to debug >> now) that it is using this certificate: >> >> 0 s:/OU=Domain Control Validated/OU=EssentialSSL >> Wildcard/CN=*.openoffice.org >> >> Note that I requested apache.org and I get a certificate valid for >> *.openoffice.org. > The subject alternative names (which are the real identities that should > match, not the common name) are '*.openoffice.org' and 'openoffice.org'. > > And you're right ... the certificate is wrong ... but making the same > request with cURL will give the right certificate. Most likely that's > because s_client doesn't send the Server Name Indication that would let > HTTPd select the correct virtual host, so it'll select the "first" one. > > >> The same holds if I use just apache.org or openoffice.org > And this tends to prove the above assumption. And so does this: $ openssl s_client -state -nbio -servername ooo-updates.apache.org -connect ooo-updates.apache.org:443 Note the additional -servename option. -- Brane - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for Updates broken?
On 18.11.2018 17:19, Andrea Pescetti wrote: > Pedro Lino wrote: >> However the AOO site does not specify any charset. Could that be the >> problem? > > I don't think the charset is a major issue, but indeed (if I do the > same test with openssl) there is something interesting that can > probably be submitted to Infra for investigation. > > On any system I've tried with (CentOS, Ubuntu, Fedora) > > $ openssl s_client -state -nbio -connect ooo-updates.apache.org:443 > > will show (in a lengthy output that I don't have the time to debug > now) that it is using this certificate: > > 0 s:/OU=Domain Control Validated/OU=EssentialSSL > Wildcard/CN=*.openoffice.org > > Note that I requested apache.org and I get a certificate valid for > *.openoffice.org. The subject alternative names (which are the real identities that should match, not the common name) are '*.openoffice.org' and 'openoffice.org'. And you're right ... the certificate is wrong ... but making the same request with cURL will give the right certificate. Most likely that's because s_client doesn't send the Server Name Indication that would let HTTPd select the correct virtual host, so it'll select the "first" one. > The same holds if I use just apache.org or openoffice.org And this tends to prove the above assumption. > This mismatch itself doesn't explain much since the connection still > works, but it probably gives a hint for asking Infra why this happens. > > The output I get is very different depending on the system I use (I > get dozens of errors on some systems, a cleaner output in Ubuntu) but > in all cases openssl manages to connect in the end. I think it's best to gather all the info in this thread and create an Infra ticket. -- Brane
Re: Check for Updates broken?
Pedro Lino wrote: However the AOO site does not specify any charset. Could that be the problem? I don't think the charset is a major issue, but indeed (if I do the same test with openssl) there is something interesting that can probably be submitted to Infra for investigation. On any system I've tried with (CentOS, Ubuntu, Fedora) $ openssl s_client -state -nbio -connect ooo-updates.apache.org:443 will show (in a lengthy output that I don't have the time to debug now) that it is using this certificate: 0 s:/OU=Domain Control Validated/OU=EssentialSSL Wildcard/CN=*.openoffice.org Note that I requested apache.org and I get a certificate valid for *.openoffice.org. The same holds if I use just apache.org or openoffice.org This mismatch itself doesn't explain much since the connection still works, but it probably gives a hint for asking Infra why this happens. The output I get is very different depending on the system I use (I get dozens of errors on some systems, a cleaner output in Ubuntu) but in all cases openssl manages to connect in the end. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Check for Updates broken?
> On November 18, 2018 at 2:48 PM Andrea Pescetti wrote: > > For debugging, I suggest using cURL instead of OO, for example: > > curl -sviI https://www.openoffice.org/ > > Thanks, if the issue is with SSL this indeed helps in finding more > details. Still, curl will always work also on affected systems, so if it > is SSL-related it won't be enough to check whether the site uses a > wildcard SSL certificate... Maybe some more technical certificate details? I compared the output from the sites that do work curl -sviI https://fosdem.org/2019/ curl -sviI https://www.google.com/ fosdem specifies < Content-Type: text/html; charset=utf-8 google specifies < Content-Type: text/html; charset=ISO-8859-1 However the AOO site does not specify any charset. Could that be the problem? On funny note, the issuer of the Google certificate is *issuer: C=US,O=Google Trust Services,CN=Google Internet Authority G3 Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: using open office
thank you very much for your help On Sunday, 18 November 2018, 14:36:19 GMT, Marcus wrote: Am 18.11.18 um 01:46 schrieb Sajan Ganger: > Hello, I would like to use OpenOffice to write a book and publish it on > amazon, do I have to pay any fees or royalties to yourselves? > Do I need a licence? Thank you very muchI look forward to hearing from you OpenOffice is built under the license of Apache [1] which is often used for open source software. There is no fee, no royalty, no license, no registration that have to give us. You can copy OpenOffice as often as you want to different PCs. And finally you can copy, upload or sell any documents that you have created with OpenOffice. [1] http://www.apache.org/licenses/LICENSE-2.0.html HTH Marcus
Re: Check for Updates broken?
Branko Čibej wrote: Note that all the sites that fail in your list have wildcard certificates — CN=*.apache.org for the Apache sites and CN=*.openoffice.org for the OO sites. This may be related to wildcard cert support Interesting find, and I was hopeful this could be the solution. But if try with fosdem.org (that has a wildcard certificate too) it works even on the Ubuntu system (i.e., the one where I cannot get the updates): $ soffice https://fosdem.org/2019/ # Works, HTTPS with wildcard in OpenSSL/LibreSSL/GnuTLS/whateveryou'reusing on the affected systems. Correlating this with the SSL library name and version would be useful. But, as reported by Pedro in the first test, $ curl https://ooo-updates.apache.org/index.html works well, while $ soffice https://ooo-updates.apache.org/index.html so it's unclear to what extent system libraries are involved. I've tried, with no success, to install more libraries $ sudo apt-get install libssl1.0-dev (see here for context: https://github.com/wkhtmltopdf/wkhtmltopdf/issues/2938#issuecomment-334784936 ) but the Ubuntu system still refused to open the update URL. For debugging, I suggest using cURL instead of OO, for example: curl -sviI https://www.openoffice.org/ Thanks, if the issue is with SSL this indeed helps in finding more details. Still, curl will always work also on affected systems, so if it is SSL-related it won't be enough to check whether the site uses a wildcard SSL certificate... Maybe some more technical certificate details? I'm now trying to check the OpenOffice code to see whether we can get some more meaningful output instead of the empty details string we currently print. For those interested, the error message is assembled in main/uui/source/iahndl.cxx Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: using open office
Am 18.11.18 um 01:46 schrieb Sajan Ganger: Hello, I would like to use OpenOffice to write a book and publish it on amazon, do I have to pay any fees or royalties to yourselves? Do I need a licence? Thank you very muchI look forward to hearing from you OpenOffice is built under the license of Apache [1] which is often used for open source software. There is no fee, no royalty, no license, no registration that have to give us. You can copy OpenOffice as often as you want to different PCs. And finally you can copy, upload or sell any documents that you have created with OpenOffice. [1] http://www.apache.org/licenses/LICENSE-2.0.html HTH Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: German language link in EN page for install instructions
Hi David, Am 18.11.18 um 08:26 schrieb David Robley: > The AOO installation page > https://www.openoffice.org/download/common/instructions.html#apple has > a link about Gatekeeper on OSX which links to a German language Apple > support page. > > Can this link please be changed to point to the English language > version, currently at https://support.apple.com/en-us/HT202491 Fixed now! Thank you for your hint... Regards, Matthias > > > Cheers smime.p7s Description: S/MIME Cryptographic Signature
