Not updating EasyFax list

[xKiv]

I believe java 7 shouldn't have the specific problem I described, but java 6 could (depending on patchlevel, and if it's oracle/openjdk/ibm java?).

[heeheehee]

$ java -version
Picked up _JAVA_OPTIONS: -Dawt.useSystemAAFontSettings=gasp
openjdk version "1.8.0_121"
OpenJDK Runtime Environment (build 1.8.0_121-b13)
OpenJDK 64-Bit Server VM (build 25.121-b13, mixed mode

I fully expect to be an outlier, since I'm running this on Linux.

That said, it could very well be an issue with an older version of Java, although that does strike me as a bit strange.

Doubly so, since from another thread:

My test:

bash-3.2$ java -jar KoLmafia-17.5.jar 

KoLmafia v17.5 r17696
Released on November 22, 2016

Currently Running on Mac OS X
Local Directory is /Users/xxx/Library/Application Support/KoLmafia
Using Java 1.8.0_121

It compiles and executes just fine with the latest Java 1.8 release.

Veracity is using at least a similar version of Java.

[Veracity]

Yes. I'm still using that version of Java.

I deleted (renamed) the old easyfax.xml and, unlike certain others, get the same stack trace trying to download the XML file.

I copied the xml file I downloaded with my browser to the data directory and KoLmafia read that successfully, at least.

[lostcalpolydude]

I updated to Java v1.8.0_131-b11 and I still get the same result.

[Veracity]

I recently upgraded my computer and tried running Eclipse for the first time - and am told that I "need to install Legacy Java 1.6" in order to do so. So, I upgraded Eclipse and am now trying to get back up to speed with my KoLmafia workspace so I can try debugging this.

[txrangersxx]

I am now getting it on Java 8 131. I can post a debug log if needed. I think my previous was because I manually downloaded the file.

[heeheehee]

Hm.

Per http://stackoverflow.com/questions/3...o-a-https-site --

Java crypto has a crock dating back to the 1990s when the US government severely restricted export of crypto software, and as a result the JRE (or JDK) as distributed by then-Sun now-Oracle does not permit use of 256-bit symmetric encryption

ssllabs indicates that sourceforge.net only supports the following cipher suites:

Cipher Suites
# TLS 1.2 (suites in server-preferred order)
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (0xc014) ECDH secp256r1 (eq. 3072 bits RSA) FS 256
TLS_RSA_WITH_AES_256_CBC_SHA (0x35) 256
TLS_RSA_WITH_AES_256_CBC_SHA256 (0x3d) 256

i.e., all of them are 256-bit.

[heeheehee]

So yeah, basically I'm an outlier because I'm running OpenJDK on Linux, which has no such restrictions. Neat.

[txrangersxx]

If you read on it says to do the following to fix it : You must download and install the "JCE Unlimited Strength Jurisdiction Policy Files" for your Java (major) version; 8 is at http://www.oracle.com/technetwork/ja...d-2133166.html . The README in the file gives longwinded details, but basically you replace two tiny jar files in JRE/lib/security.

[Veracity]

That does work.

It's a shame that sourceforge insists on using non-exportable security.