Ok so I tried to work around the problem for the largest part of the day, but it turns out not to be the certificate itself but the encryption strength sourceforge uses. It seems to require an encryption strength that the normal JDK simply can’t do, so we need our users to update the JCE, but this is not available outside of the US.
Currently I don’t see any way I could reliably fix the auto-download of fontkit without moving the files to another server. http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html Chris Am 10.02.17, 14:32 schrieb "Christofer Dutz" <christofer.d...@c-ware.de>: So as the mavenizer is having the same error when downloading the fontkit libs, I looked into this. The problem is that sourceforge seems to have switched to certificates from letsencrypt. Unfortunately, prior to 1.8.0_101 the default keystore doesn’t trust those certificates. I don’t quite know how I should address this problem. I would assume, catching the error and outputting a useful error message would be the best solution, but I doubt people would execute the measures to manually add the cert-chain or update the JDK for that. So eventually adding an “unsafe-downloads” option to disable SSL certification would be an option. Chris Am 07.02.17, 06:46 schrieb "Alex Harui" <aha...@adobe.com>: Well, the adobe downloads worked, but I could not get saxon to work. It might be time to use the Maven saxon.jar. I manually downloaded the maven jar from [1] and the build and checkintests passed. [1] http://repo1.maven.org/maven2/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1 .0.8.jar -Alex On 2/6/17, 9:00 PM, "Alex Harui" <aha...@adobe.com> wrote: >This fixed it for me: > >http://stackoverflow.com/questions/38203971/javax-net-ssl-sslhandshakeexce >p >tion-received-fatal-alert-handshake-failure/38264878#38264878 > >See the part about jce. Not sure if it is available outside the US. > >HTH, >-Alex > >On 2/6/17, 6:18 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >>Hi, >> >>BTW Chris the flex-sdk-converter is also failing with similar errors. >> >>Justin >
