Re: Openssl, serf and curl... and NSS
Hi Jim, On 2/14/22 10:04 AM, Jim Jagielski wrote: The en-US version of a dev/test of AOO 4.1.12 can be found here: http://home.apache.org/~jim/AOO-builds/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Are those linux builds 32 bit like the name implies? Apache_OpenOffice_4.1.12_Linux_x86_install-deb_en-US.tar.gz 2022-02-14 17:08 151M Apache_OpenOffice_4.1.12_Linux_x86_install-rpm_en-US.tar.gz 2022-02-14 17:08 153M Thanks, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Find the latest en-US build for Windows here: https://home.apache.org/~mseidel/Apache_OpenOffice_4.1.12_Win_x86_install_en-US_Test.exe Am 14.02.22 um 16:04 schrieb Jim Jagielski: > The en-US version of a dev/test of AOO 4.1.12 can be found here: > http://home.apache.org/~jim/AOO-builds/ > - > 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
Re: Openssl, serf and curl... and NSS
Hi Jim, Am 14.02.22 um 16:04 schrieb Jim Jagielski: > The en-US version of a dev/test of AOO 4.1.12 can be found here: > http://home.apache.org/~jim/AOO-builds/ Tested it on our Monterey/M1 machine. Looks good! And the update check is working again! ;-) Regards, Matthias > - > 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
Re: Openssl, serf and curl... and NSS
The en-US version of a dev/test of AOO 4.1.12 can be found here: http://home.apache.org/~jim/AOO-builds/ - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Jim > On 02/14/2022 12:24 PM Jim Jagielski wrote: > > > If everyone is in agreement, I'll create a macOS and Linux test/dev build of > AOO41X HEAD Please do! Actually you should put it the other way around: "If no one opposes, I'll create a macOS and Linux test/dev build of AOO41X HEAD" Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
If everyone is in agreement, I'll create a macOS and Linux test/dev build of AOO41X HEAD - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
> On Feb 10, 2022, at 1:13 PM, Matthias Seidel > wrote: > > Hi Pedro, > > Am 10.02.22 um 18:16 schrieb Pedro Lino: >> Hi Matthias, all >> >>> On 02/10/2022 4:29 PM Matthias Seidel wrote: >> >>> I think Jim has Java 7 available, since we always built AOO41X with it. >> Is there any reason for not updating to Java 8 which is still maintained? >> Maybe we can let go of Java 7? > > We shouldn't switch the JAVA version within AOO41X without decent testing. Agreed. > > Of course it builds, but I remember some problems with JavaDoc? > > Regards, > >Matthias > >> >> Regards, >> Pedro >> >> - >> 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
Re: Openssl, serf and curl... and NSS
Am 10.02.22 um 20:12 schrieb Arrigo Marchiori: Hello Carl, On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: Hi Arrigo, On 2/10/22 11:00 AM, Arrigo Marchiori wrote: Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. On Feb 8, 2022, at 6:06 AM, Matthias Seidel wrote: Hi Arrigo, No need to apologize. ;-) But I think, before we begin to think about upgrading serf we need to make sure that AOO41X is able to build successfully on all platforms. Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. What is the architecture of the Mac Mini? % uname -a Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64 Asul has x86-64 JDK's available for Java 7 but that's all. https://www.azul.com/downloads/?version=java-7-lts=macos=jdk I will try that! Please allow me to state I had no intention to ``subvert'' current versions of Java or whatever. For what I understand, Catalina and the XCode versions installed in our Mac mini do not match the reference macOS version and tools for our AOO41X builds, and this is absolutely fine for me, as long as there is someone else who has a system with the ``official'' architecture and is able to use it. I am just trying to have a (whatever version of) macOS building AOO, so that when I commit something, I can test on that architecture as well. And possibly lower the barriers to entry for others. So if any of my edits break the builds on ``official machines'', please let us just revert them. The Java version change was not even committed anywhere. ;-) Thank you for reading through my disclaimer. ;-) Don't worry. I don't see a problem for now. Great that you experiment with a different setup to see how it works then. For the AOO41X release branch we really should try as best and long as possible to keep the setup the same like the past releases to give a (kind of) guarantee that a new release would run also in the same PC environment. So, the next step is to see if the build is also successful with Java 7. But as I see this already in progress . :-) All fine Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Just a quick, small update: On Thu, Feb 10, 2022 at 08:12:02PM +0100, Arrigo Marchiori wrote: > Hello Carl, > > On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: [...] > > Asul has x86-64 JDK's available for Java 7 but that's all. > > > > https://www.azul.com/downloads/?version=java-7-lts=macos=jdk > > I will try that! Installed, detected, new build of AOO41X in progress! :-) Thank you! Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hello Carl, On Thu, Feb 10, 2022 at 11:32:57AM -0500, Carl Marcum wrote: > Hi Arrigo, > > On 2/10/22 11:00 AM, Arrigo Marchiori wrote: > > Hello Matthias, > > > > On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: > > > > > Hi Arrigo, > > > > > > Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: > > > > Dear Jim, Matthias, All, > > > > > > > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > > > > > > > > > That's right... I'll wait to even try compiling until things settle > > > > > down and we have some slowly moving target I can compile and build > > > > > against. > > > > > > > > > > > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > > > > > > wrote: > > > > > > > > > > > > Hi Arrigo, > > > > > > > > > > > > No need to apologize. ;-) > > > > > > > > > > > > But I think, before we begin to think about upgrading serf we need > > > > > > to > > > > > > make sure that AOO41X is able to build successfully on all > > > > > > platforms. > > > > > > > > > > > > Windows and Linux are OK, I think. macOS is still pending? > > > > AOO41X now builds under Catalina, with a single edit to the official > > > > build script: AOO_JAVA_VERSION=1.8 > > > So you build with Java 8? > > The official build script contains the setting: > > AOO_JAVA_VERSION=1.7 > > > > On our Mac mini, the script fails because Java 1.7 is not installed, > > and it does not seem to be available on-line for download. > > What is the architecture of the Mac Mini? % uname -a Darwin administrators-Mac-mini.local 19.6.0 Darwin Kernel Version 19.6.0: Sun Nov 14 19:58:51 PST 2021; root:xnu-6153.141.50~1/RELEASE_X86_64 x86_64 > Asul has x86-64 JDK's available for Java 7 but that's all. > > https://www.azul.com/downloads/?version=java-7-lts=macos=jdk I will try that! Please allow me to state I had no intention to ``subvert'' current versions of Java or whatever. For what I understand, Catalina and the XCode versions installed in our Mac mini do not match the reference macOS version and tools for our AOO41X builds, and this is absolutely fine for me, as long as there is someone else who has a system with the ``official'' architecture and is able to use it. I am just trying to have a (whatever version of) macOS building AOO, so that when I commit something, I can test on that architecture as well. And possibly lower the barriers to entry for others. So if any of my edits break the builds on ``official machines'', please let us just revert them. The Java version change was not even committed anywhere. ;-) Thank you for reading through my disclaimer. ;-) Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi All, On 2/10/22 1:13 PM, Matthias Seidel wrote: Hi Pedro, Am 10.02.22 um 18:16 schrieb Pedro Lino: Hi Matthias, all On 02/10/2022 4:29 PM Matthias Seidel wrote: I think Jim has Java 7 available, since we always built AOO41X with it. Is there any reason for not updating to Java 8 which is still maintained? Maybe we can let go of Java 7? I'm I correct that Arrigo was only proving the build in this particular machine ans using Java 8 because that is what was available on that machine? I don't think our official build for the 4.1 branch should change to Java 8. I'm all for dumping Java 7 on 4.2 and would support at least Java 11 on trunk if possible because Java 8 is EOL now I believe. But the Java for 4.2 and beyond is for another day. We shouldn't switch the JAVA version within AOO41X without decent testing. Or at all for the release build IMHO. Of course it builds, but I remember some problems with JavaDoc? I remember there was work done on Javadoc and it may have been from 6 to 7 but I'd have to research that. Best regards, Carl Regards, Matthias Regards, Pedro - 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
Re: Openssl, serf and curl... and NSS
Hi Pedro, Am 10.02.22 um 18:16 schrieb Pedro Lino: > Hi Matthias, all > >> On 02/10/2022 4:29 PM Matthias Seidel wrote: > >> I think Jim has Java 7 available, since we always built AOO41X with it. > Is there any reason for not updating to Java 8 which is still maintained? > Maybe we can let go of Java 7? We shouldn't switch the JAVA version within AOO41X without decent testing. Of course it builds, but I remember some problems with JavaDoc? Regards, Matthias > > Regards, > Pedro > > - > 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
Re: Openssl, serf and curl... and NSS
Hi Matthias, all > On 02/10/2022 4:29 PM Matthias Seidel wrote: > I think Jim has Java 7 available, since we always built AOO41X with it. Is there any reason for not updating to Java 8 which is still maintained? Maybe we can let go of Java 7? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, On 2/10/22 11:00 AM, Arrigo Marchiori wrote: Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. On Feb 8, 2022, at 6:06 AM, Matthias Seidel wrote: Hi Arrigo, No need to apologize. ;-) But I think, before we begin to think about upgrading serf we need to make sure that AOO41X is able to build successfully on all platforms. Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. What is the architecture of the Mac Mini? Asul has x86-64 JDK's available for Java 7 but that's all. https://www.azul.com/downloads/?version=java-7-lts=macos=jdk Thanks, Carl I found Java 8 installed, and that's why I changed the setting. I hope it makes sense. Best regards, - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, Am 10.02.22 um 17:00 schrieb Arrigo Marchiori: > Hello Matthias, > > On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: > >> Hi Arrigo, >> >> Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: >>> Dear Jim, Matthias, All, >>> >>> On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: >>> That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > wrote: > > Hi Arrigo, > > No need to apologize. ;-) > > But I think, before we begin to think about upgrading serf we need to > make sure that AOO41X is able to build successfully on all platforms. > > Windows and Linux are OK, I think. macOS is still pending? >>> AOO41X now builds under Catalina, with a single edit to the official >>> build script: AOO_JAVA_VERSION=1.8 >> So you build with Java 8? > The official build script contains the setting: > AOO_JAVA_VERSION=1.7 > > On our Mac mini, the script fails because Java 1.7 is not installed, > and it does not seem to be available on-line for download. > > I found Java 8 installed, and that's why I changed the setting. > > I hope it makes sense. Thanks for the clarification. I think Jim has Java 7 available, since we always built AOO41X with it. Regards, Matthias > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Hello Matthias, On Thu, Feb 10, 2022 at 03:42:16PM +0100, Matthias Seidel wrote: > Hi Arrigo, > > Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: > > Dear Jim, Matthias, All, > > > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > > > >> That's right... I'll wait to even try compiling until things settle > >> down and we have some slowly moving target I can compile and build > >> against. > >> > >>> On Feb 8, 2022, at 6:06 AM, Matthias Seidel > >>> wrote: > >>> > >>> Hi Arrigo, > >>> > >>> No need to apologize. ;-) > >>> > >>> But I think, before we begin to think about upgrading serf we need to > >>> make sure that AOO41X is able to build successfully on all platforms. > >>> > >>> Windows and Linux are OK, I think. macOS is still pending? > > AOO41X now builds under Catalina, with a single edit to the official > > build script: AOO_JAVA_VERSION=1.8 > > So you build with Java 8? The official build script contains the setting: AOO_JAVA_VERSION=1.7 On our Mac mini, the script fails because Java 1.7 is not installed, and it does not seem to be available on-line for download. I found Java 8 installed, and that's why I changed the setting. I hope it makes sense. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, Am 10.02.22 um 15:21 schrieb Arrigo Marchiori: > Dear Jim, Matthias, All, > > On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > >> That's right... I'll wait to even try compiling until things settle >> down and we have some slowly moving target I can compile and build >> against. >> >>> On Feb 8, 2022, at 6:06 AM, Matthias Seidel >>> wrote: >>> >>> Hi Arrigo, >>> >>> No need to apologize. ;-) >>> >>> But I think, before we begin to think about upgrading serf we need to >>> make sure that AOO41X is able to build successfully on all platforms. >>> >>> Windows and Linux are OK, I think. macOS is still pending? > AOO41X now builds under Catalina, with a single edit to the official > build script: AOO_JAVA_VERSION=1.8 So you build with Java 8? Regards, Matthias > > I suggest this is a good candidate. Please note that the serf upgrade > is _not_ yet merged. > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Dear Jim, Matthias, All, On Wed, Feb 09, 2022 at 12:12:09PM -0500, Jim Jagielski wrote: > That's right... I'll wait to even try compiling until things settle > down and we have some slowly moving target I can compile and build > against. > > > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > > wrote: > > > > Hi Arrigo, > > > > No need to apologize. ;-) > > > > But I think, before we begin to think about upgrading serf we need to > > make sure that AOO41X is able to build successfully on all platforms. > > > > Windows and Linux are OK, I think. macOS is still pending? AOO41X now builds under Catalina, with a single edit to the official build script: AOO_JAVA_VERSION=1.8 I suggest this is a good candidate. Please note that the serf upgrade is _not_ yet merged. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
That's right... I'll wait to even try compiling until things settle down and we have some slowly moving target I can compile and build against. > On Feb 8, 2022, at 6:06 AM, Matthias Seidel > wrote: > > Hi Arrigo, > > No need to apologize. ;-) > > But I think, before we begin to think about upgrading serf we need to > make sure that AOO41X is able to build successfully on all platforms. > > Windows and Linux are OK, I think. macOS is still pending? > > Regards, > >Matthias > > Am 07.02.22 um 08:14 schrieb Arrigo Marchiori: >> Hello Pedro, >> >> On Sun, Feb 06, 2022 at 09:39:19PM +, Pedro Lino wrote: >> >>> Hi Arrigo >>> On 02/06/2022 9:24 PM Arrigo Marchiori wrote: If anyone can reproduce the problem, i.e. has -- or can set up -- a WebDAV server with https access, I can provide a build for testing. >>> What problem? I use AOO to edit files on webdav. >> Isn't this bug about WebDAV? >> https://bz.apache.org/ooo/show_bug.cgi?id=126312 >> >> >>> I have just used build >>> AOO4112m1(Build:9809) - Rev. 1986472fd5 >>> 2022-02-03_12:29:43 - Rev. 1986472fd5882e9c172fd1e6628697ec0c37d322 >>> >>> to edit a file in >>> https://dav.mailbox.org/servlet/webdav.infostore/Userstore/Pedro%20Lino/Documents/ >>> >>> without any problems. >> According to your and Matthias' results, then it has to be something >> tied to NTML _and_ WebDAV. I apologize for being inaccurate. >> >> Best regards, > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, No need to apologize. ;-) But I think, before we begin to think about upgrading serf we need to make sure that AOO41X is able to build successfully on all platforms. Windows and Linux are OK, I think. macOS is still pending? Regards, Matthias Am 07.02.22 um 08:14 schrieb Arrigo Marchiori: > Hello Pedro, > > On Sun, Feb 06, 2022 at 09:39:19PM +, Pedro Lino wrote: > >> Hi Arrigo >> >>> On 02/06/2022 9:24 PM Arrigo Marchiori wrote: >>> If anyone can reproduce the problem, i.e. has -- or can set up -- a >>> WebDAV server with https access, I can provide a build for testing. >> What problem? I use AOO to edit files on webdav. > Isn't this bug about WebDAV? > https://bz.apache.org/ooo/show_bug.cgi?id=126312 > > >> I have just used build >> AOO4112m1(Build:9809) - Rev. 1986472fd5 >> 2022-02-03_12:29:43 - Rev. 1986472fd5882e9c172fd1e6628697ec0c37d322 >> >> to edit a file in >> https://dav.mailbox.org/servlet/webdav.infostore/Userstore/Pedro%20Lino/Documents/ >> >> without any problems. > According to your and Matthias' results, then it has to be something > tied to NTML _and_ WebDAV. I apologize for being inaccurate. > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Hello Pedro, On Sun, Feb 06, 2022 at 09:39:19PM +, Pedro Lino wrote: > Hi Arrigo > > > On 02/06/2022 9:24 PM Arrigo Marchiori wrote: > > > If anyone can reproduce the problem, i.e. has -- or can set up -- a > > WebDAV server with https access, I can provide a build for testing. > > What problem? I use AOO to edit files on webdav. Isn't this bug about WebDAV? https://bz.apache.org/ooo/show_bug.cgi?id=126312 > I have just used build > AOO4112m1(Build:9809) - Rev. 1986472fd5 > 2022-02-03_12:29:43 - Rev. 1986472fd5882e9c172fd1e6628697ec0c37d322 > > to edit a file in > https://dav.mailbox.org/servlet/webdav.infostore/Userstore/Pedro%20Lino/Documents/ > > without any problems. According to your and Matthias' results, then it has to be something tied to NTML _and_ WebDAV. I apologize for being inaccurate. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo > On 02/06/2022 9:24 PM Arrigo Marchiori wrote: > If anyone can reproduce the problem, i.e. has -- or can set up -- a > WebDAV server with https access, I can provide a build for testing. What problem? I use AOO to edit files on webdav. I have just used build AOO4112m1(Build:9809) - Rev. 1986472fd5 2022-02-03_12:29:43 - Rev. 1986472fd5882e9c172fd1e6628697ec0c37d322 to edit a file in https://dav.mailbox.org/servlet/webdav.infostore/Userstore/Pedro%20Lino/Documents/ without any problems. Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, Am 06.02.22 um 22:24 schrieb Arrigo Marchiori: > Hello, > > On Fri, Feb 04, 2022 at 06:06:10PM +0100, Matthias Seidel wrote: > >> Hi Peter, >> >> Am 04.02.22 um 17:59 schrieb Peter Kovacs: >>> Can then someone check if this is resolved? >>> >>> https://bz.apache.org/ooo/show_bug.cgi?id=126312 >> I don't think so. Until now we upgraded nss. But Arrigo is working on >> his branch to upgrade serf, I think. > Yes, the "serf" branch exists for this purpose. > > If anyone can reproduce the problem, i.e. has -- or can set up -- a > WebDAV server with https access, I can provide a build for testing. I have just connected successfully to a NextCloud server via WebDAV with https. This worked with a build from trunk on Windows. But this NextCloud server has is own authentication, I think the issue is about Windows authentication. NextCloud would need to be in sync with Active Directory then... Regards, Matthias > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Hello, On Fri, Feb 04, 2022 at 06:06:10PM +0100, Matthias Seidel wrote: > Hi Peter, > > Am 04.02.22 um 17:59 schrieb Peter Kovacs: > > Can then someone check if this is resolved? > > > > https://bz.apache.org/ooo/show_bug.cgi?id=126312 > > I don't think so. Until now we upgraded nss. But Arrigo is working on > his branch to upgrade serf, I think. Yes, the "serf" branch exists for this purpose. If anyone can reproduce the problem, i.e. has -- or can set up -- a WebDAV server with https access, I can provide a build for testing. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Pedro, Am 06.02.22 um 21:26 schrieb Pedro Lino: > Hi Matthias > >> On 02/04/2022 6:41 AM Matthias Seidel wrote: >>> I will install it on my "brand new" Ubuntu 20.04.3 tomorrow >> That might look a bit odd since 20.04 introduced some kind of scaling >> factor in the UI. This is known, but it would need someone to fix it... ;-) > I don't see any scaling oddity. Can you show me what you mean? The menu bar were be higher than needed, and the sidebar looked like this for me: https://home.apache.org/~mseidel/AOO420-Ubuntu2004.png The bounding boxes overlap. This is only on Ubuntu with GNOME, looks normal on Xubuntu with XFCE. > > One thing that I don't understand is what the "Automatic" Icon size does. The > Icon size is always set to Small regardless of the screen > density/resolution... Shouldn't it switch to Large on a FullHD display? At > what ppi/resolution value is it set to switch? I have no idea... ;-) Regards, Matthias > > Regards, > Pedro > > - > 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
Re: Openssl, serf and curl... and NSS
Hi Matthias > On 02/04/2022 6:41 AM Matthias Seidel wrote: > > I will install it on my "brand new" Ubuntu 20.04.3 tomorrow > > That might look a bit odd since 20.04 introduced some kind of scaling > factor in the UI. This is known, but it would need someone to fix it... ;-) I don't see any scaling oddity. Can you show me what you mean? One thing that I don't understand is what the "Automatic" Icon size does. The Icon size is always set to Small regardless of the screen density/resolution... Shouldn't it switch to Large on a FullHD display? At what ppi/resolution value is it set to switch? Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Peter, Am 04.02.22 um 17:59 schrieb Peter Kovacs: > Can then someone check if this is resolved? > > https://bz.apache.org/ooo/show_bug.cgi?id=126312 I don't think so. Until now we upgraded nss. But Arrigo is working on his branch to upgrade serf, I think. Regards, Matthias > > > Thx. > > All the Best > > Peter > > On 03.02.22 16:00, Matthias Seidel wrote: >> Fresh new Windows builds: >> >> https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ >> >> Regards, >> >> Matthias >> >> Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: >>> On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: >>> Hello Matthias, On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > Hi Arrigo, > > Can the changes to trunk be cherry-picked for AOO42X? Done. >>> Linux build available here: >>> http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 >>> >>> >>> Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Can then someone check if this is resolved? https://bz.apache.org/ooo/show_bug.cgi?id=126312 Thx. All the Best Peter On 03.02.22 16:00, Matthias Seidel wrote: Fresh new Windows builds: https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ Regards, Matthias Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: Hello Matthias, On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: Hi Arrigo, Can the changes to trunk be cherry-picked for AOO42X? Done. Linux build available here: http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 Best regards, -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Pedro, Am 03.02.22 um 23:18 schrieb Pedro Lino: > Hi Matthias > > >> On 02/03/2022 7:48 PM Matthias Seidel wrote: >> Build is finished but it doesn't start on my ancient Ubuntu 16.04: >> >> The application cannot be started. >> exception occured raising singleton >> "/singletons/com.sun.star.deployment.ExtensionManager": loading >> component library failed: >> file:///opt/openoffice4/program/../program/deployment.uno.so > Installed without any issues on my ancient Ubuntu 18.04.6 x64 and checking > for updates and extensions (except for Marco's English dictionaries) worked > as expected. I can now confirm after installing AOO 4.1.12-dev on Ubuntu 18.04 in a VM. Update feed is working again, this is important for a new release. > I will install it on my "brand new" Ubuntu 20.04.3 tomorrow That might look a bit odd since 20.04 introduced some kind of scaling factor in the UI. This is known, but it would need someone to fix it... ;-) Regards, Matthias > > Regards, > Pedro > > - > 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
Re: Openssl, serf and curl... and NSS
Hi Pedro, Am 03.02.22 um 23:18 schrieb Pedro Lino: > Hi Matthias > > >> On 02/03/2022 7:48 PM Matthias Seidel wrote: >> Build is finished but it doesn't start on my ancient Ubuntu 16.04: >> >> The application cannot be started. >> exception occured raising singleton >> "/singletons/com.sun.star.deployment.ExtensionManager": loading >> component library failed: >> file:///opt/openoffice4/program/../program/deployment.uno.so > Installed without any issues on my ancient Ubuntu 18.04.6 x64 and checking > for updates and extensions (except for Marco's English dictionaries) worked > as expected. That is good to hear! The problem with update check seems to be fixed. I wonder why it does not run on Ubuntu 16.04? The problem may be the Ubuntu version of the buildbot... Regards, Matthias > I will install it on my "brand new" Ubuntu 20.04.3 tomorrow > > Regards, > Pedro > > - > 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
Re: Openssl, serf and curl... and NSS
Hi Matthias > On 02/03/2022 7:48 PM Matthias Seidel wrote: > Build is finished but it doesn't start on my ancient Ubuntu 16.04: > > The application cannot be started. > exception occured raising singleton > "/singletons/com.sun.star.deployment.ExtensionManager": loading > component library failed: > file:///opt/openoffice4/program/../program/deployment.uno.so Installed without any issues on my ancient Ubuntu 18.04.6 x64 and checking for updates and extensions (except for Marco's English dictionaries) worked as expected. I will install it on my "brand new" Ubuntu 20.04.3 tomorrow Regards, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Pedro, Am 03.02.22 um 18:15 schrieb Pedro Lino: > Thank you! > > I will try it later today Build is finished but it doesn't start on my ancient Ubuntu 16.04: The application cannot be started. exception occured raising singleton "/singletons/com.sun.star.deployment.ExtensionManager": loading component library failed: file:///opt/openoffice4/program/../program/deployment.uno.so Maybe you have better luck? Regards, Matthias > > Regards, > Pedro > >> On 02/03/2022 5:06 PM Matthias Seidel wrote: >> >> >> Am 03.02.22 um 18:00 schrieb Pedro Lino: >>> Thanks! >>> >>> Can I just compile branch 41X to get a Linux build? >> The buildbot is already building if someone wants to try later: >> >> https://nightlies.apache.org/openoffice/install/linsnap-41x/?C=M;O=D >> >> Regards, >> >> Matthias >> >>> Regards, >>> Pedro >>> On 02/03/2022 3:00 PM Matthias Seidel wrote: Fresh new Windows builds: https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ Regards, Matthias Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: > On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: > >> Hello Matthias, >> >> On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: >> >>> Hi Arrigo, >>> >>> Can the changes to trunk be cherry-picked for AOO42X? >> Done. > Linux build available here: > http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 > > Best regards, >>> - >>> 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
Re: Openssl, serf and curl... and NSS
Thank you! I will try it later today Regards, Pedro > On 02/03/2022 5:06 PM Matthias Seidel wrote: > > > Am 03.02.22 um 18:00 schrieb Pedro Lino: > > Thanks! > > > > Can I just compile branch 41X to get a Linux build? > > The buildbot is already building if someone wants to try later: > > https://nightlies.apache.org/openoffice/install/linsnap-41x/?C=M;O=D > > Regards, > > Matthias > > > > > Regards, > > Pedro > > > >> On 02/03/2022 3:00 PM Matthias Seidel wrote: > >> > >> > >> Fresh new Windows builds: > >> > >> https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ > >> > >> Regards, > >> > >> Matthias > >> > >> Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: > >>> On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: > >>> > Hello Matthias, > > On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > > > Hi Arrigo, > > > > Can the changes to trunk be cherry-picked for AOO42X? > Done. > >>> Linux build available here: > >>> http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 > >>> > >>> Best regards, > > - > > 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
Re: Openssl, serf and curl... and NSS
Am 03.02.22 um 18:00 schrieb Pedro Lino: > Thanks! > > Can I just compile branch 41X to get a Linux build? The buildbot is already building if someone wants to try later: https://nightlies.apache.org/openoffice/install/linsnap-41x/?C=M;O=D Regards, Matthias > > Regards, > Pedro > >> On 02/03/2022 3:00 PM Matthias Seidel wrote: >> >> >> Fresh new Windows builds: >> >> https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ >> >> Regards, >> >> Matthias >> >> Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: >>> On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: >>> Hello Matthias, On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > Hi Arrigo, > > Can the changes to trunk be cherry-picked for AOO42X? Done. >>> Linux build available here: >>> http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 >>> >>> Best regards, > - > 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
Re: Openssl, serf and curl... and NSS
Hi Pedro, that *should* work. Regards, Matthias Am 03.02.22 um 18:00 schrieb Pedro Lino: > Thanks! > > Can I just compile branch 41X to get a Linux build? > > Regards, > Pedro > >> On 02/03/2022 3:00 PM Matthias Seidel wrote: >> >> >> Fresh new Windows builds: >> >> https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ >> >> Regards, >> >> Matthias >> >> Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: >>> On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: >>> Hello Matthias, On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > Hi Arrigo, > > Can the changes to trunk be cherry-picked for AOO42X? Done. >>> Linux build available here: >>> http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 >>> >>> Best regards, > - > 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
Re: Openssl, serf and curl... and NSS
Thanks! Can I just compile branch 41X to get a Linux build? Regards, Pedro > On 02/03/2022 3:00 PM Matthias Seidel wrote: > > > Fresh new Windows builds: > > https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ > > Regards, > > Matthias > > Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: > > On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: > > > >> Hello Matthias, > >> > >> On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > >> > >>> Hi Arrigo, > >>> > >>> Can the changes to trunk be cherry-picked for AOO42X? > >> Done. > > Linux build available here: > > http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 > > > > Best regards, - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Fresh new Windows builds: https://home.apache.org/~mseidel/AOO-builds/AOO-4112-Test/ Regards, Matthias Am 31.01.22 um 21:36 schrieb Arrigo Marchiori: > On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: > >> Hello Matthias, >> >> On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: >> >>> Hi Arrigo, >>> >>> Can the changes to trunk be cherry-picked for AOO42X? >> Done. > Linux build available here: > http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
On Sun, Jan 30, 2022 at 10:29:57PM +0100, Arrigo Marchiori wrote: > Hello Matthias, > > On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > > > Hi Arrigo, > > > > Can the changes to trunk be cherry-picked for AOO42X? > > Done. Linux build available here: http://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-31-x86_64-installed.tar.bz2 Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hello Matthias, On Sun, Jan 30, 2022 at 05:55:26PM +0100, Matthias Seidel wrote: > Hi Arrigo, > > Can the changes to trunk be cherry-picked for AOO42X? Done. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo, Can the changes to trunk be cherry-picked for AOO42X? Regards, Matthias Am 30.01.22 um 16:08 schrieb Arrigo Marchiori: > Hello Pedro, > > On Sun, Jan 30, 2022 at 11:12:33AM +, Pedro Lino wrote: > >> Hi Arrigo >> >>> On 01/30/2022 9:32 AM Arrigo Marchiori wrote: > If I build from his branch, I get the much awaited "already up to > date" message! >> I downloaded your tar.bz2 and both Updates (program and extensions) are >> working as expected under Linux x64 (in this case under Ubuntu 20.04.3). >> Well done! > Thank you! I just merged Don's work ;-) > >>> Do we want to work on merging the 'serf' branch now, or shall we wait? >> Wouldn't it be better to fix for Mac before merging? > Absolutely! > > But I am stuck here: the "serf" branch forks from trunk. At the > moment, I cannot build trunk under MacOS; I only have a system able to > build AOO41X. > > So I need somebody else's help to validate the serf branch on macOS. > > Best regards, smime.p7s Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Hello Pedro, On Sun, Jan 30, 2022 at 11:12:33AM +, Pedro Lino wrote: > Hi Arrigo > > > On 01/30/2022 9:32 AM Arrigo Marchiori wrote: > > > > > If I build from his branch, I get the much awaited "already up to > > > > date" message! > > I downloaded your tar.bz2 and both Updates (program and extensions) are > working as expected under Linux x64 (in this case under Ubuntu 20.04.3). > Well done! Thank you! I just merged Don's work ;-) > > Do we want to work on merging the 'serf' branch now, or shall we wait? > > Wouldn't it be better to fix for Mac before merging? Absolutely! But I am stuck here: the "serf" branch forks from trunk. At the moment, I cannot build trunk under MacOS; I only have a system able to build AOO41X. So I need somebody else's help to validate the serf branch on macOS. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi Arrigo > On 01/30/2022 9:32 AM Arrigo Marchiori wrote: > > > If I build from his branch, I get the much awaited "already up to > > > date" message! I downloaded your tar.bz2 and both Updates (program and extensions) are working as expected under Linux x64 (in this case under Ubuntu 20.04.3). Well done! > Do we want to work on merging the 'serf' branch now, or shall we wait? Wouldn't it be better to fix for Mac before merging? Thank you for your persistence! All the best, Pedro - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Dear All, On Fri, Jan 07, 2022 at 05:21:50PM +0100, Peter Kovacs wrote: > On 07.01.22 13:47, Arrigo Marchiori wrote: [...] > > Don Lewis' proposed update to NSS seem to fix this problem! > > If I build from his branch, I get the much awaited "already up to > > date" message! > > Proof: > > https://home.apache.org/~ardovm/openoffice/linux/openoffice4-nss-x86_64-2022-01-07-installed.tar.bz2 > > > > So, the way to go is probably the one I had just excluded in the first > > place: > > > > 0- update NSS as per https://github.com/apache/openoffice/pull/100 > cool if it works merge it. Done! Test builds od AOO41X: - Linux: https://home.apache.org/~ardovm/openoffice/linux/openoffice4-2022-01-30-x86_64-installed.tar.bz2 - Windows: https://home.apache.org/~ardovm/openoffice/windows/Apache_OpenOffice_2022-01-30_Win_x86_install_en-US.exe macOS is still WIP. Do we want to work on merging the 'serf' branch now, or shall we wait? Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
On 07.01.22 13:47, Arrigo Marchiori wrote:
Hello Peter, All,
On Thu, Jan 06, 2022 at 09:34:22PM +0100, Peter Kovacs wrote:
On 06.01.22 16:04, Arrigo Marchiori wrote:
Dear All,
On Thu, Jan 06, 2022 at 03:02:21PM +0100, Arrigo Marchiori wrote:
Dear All,
On Wed, Jan 05, 2022 at 05:03:44PM +0100, Arrigo Marchiori wrote:
Dear All,
one more status update.
On Sat, Dec 25, 2021 at 09:57:03PM +0100, Arrigo Marchiori wrote:
Dear All,
first of all: merry Christmas!
On Thu, Dec 09, 2021 at 06:00:58PM +, Pedro Lino wrote:
Hi Matthias
On 12/09/2021 3:20 PM Matthias Seidel wrote:
Is this a real machine or a VM?
It is a real machine
I ask, because I have seen the Update Feed fail on Ubuntu in a VM when
it definitely worked on my Laptop.
There were a lot of errors during unpack, as I said.
What kind of errors? Maybe permission issues?
I hope I will eventually get a trunk build right for everyone...
By the way the problem _under Linux_ may or may not be due to
TLS... in fact the error message is "Device or resource busy". There
is something _inside_ serf that is failing; I am not sure it is a
network protocol issue.
I am looking into this issue in my available time.
It's true that the returned value (16) corresponds to "Device or
resource busy"... but it _also_ corresponds to
SERF_SSL_CERT_UNKNOWN_FAILURE ! And _this_ is the error!
This error is raised during the verification of the SSL certificate
chain. We are in method SerfSession::verifySerfCertificateChain().
Apparently, we have a certificate with subject "CN=*.apache.org" and
we are asking our certificate container if it "has" and "trusts" such
certificate for URL ooo-updates.apache.org.
The call (simply described) is:
CertificateContainer::hasCertificate("ooo-updates.apache.org",
"*.apache.org")
Surprisingly (to me at least), this returns
security::CertificateContainerStatus_UNTRUSTED
This breaks the update request process.
The culprit is the nss library. Our method
SecurityEnvironment_NssImpl::verifyCertificate calls
CERT_PKIXVerifyCert() that returns failure. The reason is error -8172,
"Peer's certificate issuer has been marked as not trusted by the user."
The problem is that NSS does not have access to an updated list of
certification authorities.
NSS has its own built-in list of CA's that is stored inside library
libnssckbi.so. Such list does not include the CA used by our update
server. For this reason, the check for updates fails as described.
There are two possible solutions, given the fact that we may not be
able to update our NSS to the latest and greatest version:
1- patch the latest CA list from current NSS into our NSS. I did it
for the purpose of this development, and... it is horrible. We have
to shave away some attributes that are not supported by our NSS:
- CKA_NSS_SERVER_DISTRUST_AFTER
- CKA_NSS_EMAIL_DISTRUST_AFTER
- CKA_NSS_MOZILLA_CA_POLICY
and I would not feel ``safe'' for our end-users if we did so.
2- try to access the system-level CA list, that every system should
have.
I think that 2- is the way to go.
Just an unqalified question, can we use OpenSSL instead?
I am not sure how much the functionalities of NSS and OpenSSL overlap.
It is true that we already have a codebase supporting NSS, and that
NSS is fairly widespread IMHO. If possible, I prefer remaining with
NSS.
sure, it is a dependency we have to maintain of some sort. Since we will
not use the edge Version.
So I thought if it is not working we could try to make it obsolete. But
you got it otherwise. nice.
And... you know what?
Don Lewis' proposed update to NSS seem to fix this problem!
If I build from his branch, I get the much awaited "already up to
date" message!
Proof:
https://home.apache.org/~ardovm/openoffice/linux/openoffice4-nss-x86_64-2022-01-07-installed.tar.bz2
So, the way to go is probably the one I had just excluded in the first
place:
0- update NSS as per https://github.com/apache/openoffice/pull/100
cool if it works merge it.
Best regards,
--
This is the Way! http://www.apache.org/theapacheway/index.html
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Openssl, serf and curl... and NSS
Hi all,
+1 for fixing the macOS issues and merging PR100.
Regards,
Matthias
Am 07.01.22 um 13:47 schrieb Arrigo Marchiori:
> Hello Peter, All,
>
> On Thu, Jan 06, 2022 at 09:34:22PM +0100, Peter Kovacs wrote:
>
>> On 06.01.22 16:04, Arrigo Marchiori wrote:
>>> Dear All,
>>>
>>> On Thu, Jan 06, 2022 at 03:02:21PM +0100, Arrigo Marchiori wrote:
>>>
Dear All,
On Wed, Jan 05, 2022 at 05:03:44PM +0100, Arrigo Marchiori wrote:
> Dear All,
>
> one more status update.
>
> On Sat, Dec 25, 2021 at 09:57:03PM +0100, Arrigo Marchiori wrote:
>
>> Dear All,
>>
>> first of all: merry Christmas!
>>
>> On Thu, Dec 09, 2021 at 06:00:58PM +, Pedro Lino wrote:
>>
>>> Hi Matthias
>>>
On 12/09/2021 3:20 PM Matthias Seidel
wrote:
Is this a real machine or a VM?
>>> It is a real machine
I ask, because I have seen the Update Feed fail on Ubuntu in a VM when
it definitely worked on my Laptop.
>>> There were a lot of errors during unpack, as I said.
>> What kind of errors? Maybe permission issues?
>> I hope I will eventually get a trunk build right for everyone...
>>
>> By the way the problem _under Linux_ may or may not be due to
>> TLS... in fact the error message is "Device or resource busy". There
>> is something _inside_ serf that is failing; I am not sure it is a
>> network protocol issue.
>>
>> I am looking into this issue in my available time.
> It's true that the returned value (16) corresponds to "Device or
> resource busy"... but it _also_ corresponds to
> SERF_SSL_CERT_UNKNOWN_FAILURE ! And _this_ is the error!
>
> This error is raised during the verification of the SSL certificate
> chain. We are in method SerfSession::verifySerfCertificateChain().
> Apparently, we have a certificate with subject "CN=*.apache.org" and
> we are asking our certificate container if it "has" and "trusts" such
> certificate for URL ooo-updates.apache.org.
>
> The call (simply described) is:
> CertificateContainer::hasCertificate("ooo-updates.apache.org",
> "*.apache.org")
>
> Surprisingly (to me at least), this returns
> security::CertificateContainerStatus_UNTRUSTED
>
> This breaks the update request process.
The culprit is the nss library. Our method
SecurityEnvironment_NssImpl::verifyCertificate calls
CERT_PKIXVerifyCert() that returns failure. The reason is error -8172,
"Peer's certificate issuer has been marked as not trusted by the user."
>>> The problem is that NSS does not have access to an updated list of
>>> certification authorities.
>>>
>>> NSS has its own built-in list of CA's that is stored inside library
>>> libnssckbi.so. Such list does not include the CA used by our update
>>> server. For this reason, the check for updates fails as described.
>>>
>>> There are two possible solutions, given the fact that we may not be
>>> able to update our NSS to the latest and greatest version:
>>>
>>> 1- patch the latest CA list from current NSS into our NSS. I did it
>>> for the purpose of this development, and... it is horrible. We have
>>> to shave away some attributes that are not supported by our NSS:
>>> - CKA_NSS_SERVER_DISTRUST_AFTER
>>> - CKA_NSS_EMAIL_DISTRUST_AFTER
>>> - CKA_NSS_MOZILLA_CA_POLICY
>>> and I would not feel ``safe'' for our end-users if we did so.
>>>
>>> 2- try to access the system-level CA list, that every system should
>>> have.
>>>
>>> I think that 2- is the way to go.
>> Just an unqalified question, can we use OpenSSL instead?
> I am not sure how much the functionalities of NSS and OpenSSL overlap.
>
> It is true that we already have a codebase supporting NSS, and that
> NSS is fairly widespread IMHO. If possible, I prefer remaining with
> NSS.
>
> And... you know what?
>
> Don Lewis' proposed update to NSS seem to fix this problem!
> If I build from his branch, I get the much awaited "already up to
> date" message!
> Proof:
> https://home.apache.org/~ardovm/openoffice/linux/openoffice4-nss-x86_64-2022-01-07-installed.tar.bz2
>
> So, the way to go is probably the one I had just excluded in the first
> place:
>
> 0- update NSS as per https://github.com/apache/openoffice/pull/100
>
> Best regards,
smime.p7s
Description: S/MIME Cryptographic Signature
Re: Openssl, serf and curl... and NSS
Hello Peter, All,
On Thu, Jan 06, 2022 at 09:34:22PM +0100, Peter Kovacs wrote:
>
> On 06.01.22 16:04, Arrigo Marchiori wrote:
> > Dear All,
> >
> > On Thu, Jan 06, 2022 at 03:02:21PM +0100, Arrigo Marchiori wrote:
> >
> > > Dear All,
> > >
> > > On Wed, Jan 05, 2022 at 05:03:44PM +0100, Arrigo Marchiori wrote:
> > >
> > > > Dear All,
> > > >
> > > > one more status update.
> > > >
> > > > On Sat, Dec 25, 2021 at 09:57:03PM +0100, Arrigo Marchiori wrote:
> > > >
> > > > > Dear All,
> > > > >
> > > > > first of all: merry Christmas!
> > > > >
> > > > > On Thu, Dec 09, 2021 at 06:00:58PM +, Pedro Lino wrote:
> > > > >
> > > > > > Hi Matthias
> > > > > >
> > > > > > > On 12/09/2021 3:20 PM Matthias Seidel
> > > > > > > wrote:
> > > > > > > Is this a real machine or a VM?
> > > > > > It is a real machine
> > > > > > > I ask, because I have seen the Update Feed fail on Ubuntu in a VM
> > > > > > > when
> > > > > > > it definitely worked on my Laptop.
> > > > > > There were a lot of errors during unpack, as I said.
> > > > > What kind of errors? Maybe permission issues?
> > > > > I hope I will eventually get a trunk build right for everyone...
> > > > >
> > > > > By the way the problem _under Linux_ may or may not be due to
> > > > > TLS... in fact the error message is "Device or resource busy". There
> > > > > is something _inside_ serf that is failing; I am not sure it is a
> > > > > network protocol issue.
> > > > >
> > > > > I am looking into this issue in my available time.
> > > > It's true that the returned value (16) corresponds to "Device or
> > > > resource busy"... but it _also_ corresponds to
> > > > SERF_SSL_CERT_UNKNOWN_FAILURE ! And _this_ is the error!
> > > >
> > > > This error is raised during the verification of the SSL certificate
> > > > chain. We are in method SerfSession::verifySerfCertificateChain().
> > > > Apparently, we have a certificate with subject "CN=*.apache.org" and
> > > > we are asking our certificate container if it "has" and "trusts" such
> > > > certificate for URL ooo-updates.apache.org.
> > > >
> > > > The call (simply described) is:
> > > > CertificateContainer::hasCertificate("ooo-updates.apache.org",
> > > > "*.apache.org")
> > > >
> > > > Surprisingly (to me at least), this returns
> > > > security::CertificateContainerStatus_UNTRUSTED
> > > >
> > > > This breaks the update request process.
> > > The culprit is the nss library. Our method
> > > SecurityEnvironment_NssImpl::verifyCertificate calls
> > > CERT_PKIXVerifyCert() that returns failure. The reason is error -8172,
> > > "Peer's certificate issuer has been marked as not trusted by the user."
> > The problem is that NSS does not have access to an updated list of
> > certification authorities.
> >
> > NSS has its own built-in list of CA's that is stored inside library
> > libnssckbi.so. Such list does not include the CA used by our update
> > server. For this reason, the check for updates fails as described.
> >
> > There are two possible solutions, given the fact that we may not be
> > able to update our NSS to the latest and greatest version:
> >
> > 1- patch the latest CA list from current NSS into our NSS. I did it
> > for the purpose of this development, and... it is horrible. We have
> > to shave away some attributes that are not supported by our NSS:
> > - CKA_NSS_SERVER_DISTRUST_AFTER
> > - CKA_NSS_EMAIL_DISTRUST_AFTER
> > - CKA_NSS_MOZILLA_CA_POLICY
> > and I would not feel ``safe'' for our end-users if we did so.
> >
> > 2- try to access the system-level CA list, that every system should
> > have.
> >
> > I think that 2- is the way to go.
> Just an unqalified question, can we use OpenSSL instead?
I am not sure how much the functionalities of NSS and OpenSSL overlap.
It is true that we already have a codebase supporting NSS, and that
NSS is fairly widespread IMHO. If possible, I prefer remaining with
NSS.
And... you know what?
Don Lewis' proposed update to NSS seem to fix this problem!
If I build from his branch, I get the much awaited "already up to
date" message!
Proof:
https://home.apache.org/~ardovm/openoffice/linux/openoffice4-nss-x86_64-2022-01-07-installed.tar.bz2
So, the way to go is probably the one I had just excluded in the first
place:
0- update NSS as per https://github.com/apache/openoffice/pull/100
Best regards,
--
Arrigo
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
