Hi there!
One of our members recently discovered an issue with running a Big Dig server with a recent Java 8 version: it wouldn't start. Minecraft Forge certificates wouldn't load, none of the mod jar certificates would load, and eventually the mods themselves would abort the server startup due to the missing certificates, claiming that they were manipulated versions.
After some investigation, we discovered that was happening due to Java 8u351 dropping support for SHA-1 JAR signatures, which is apparently what Forge and the mods had.
A workaround for that issue is changing the Java security settings to allow SHA-1 JAR signatures again, which involves creating a file, and using a JVM argument to load those security settings.
That's exactly what we did for the Big Dig server packages: we created a legacy.security file with the correct override for jdk.jar.disabledAlgorithms, and we passed it to Java using -Djava.security.properties=legacy.security, therefore enabling Big Dig servers to run on Java 8u351+.
Changes will likely be required for Technic Launcher as well, since users who aren't using Mojang JREs and have a Java version more recent than that will also experience the same issue. The same workaround would work, however. We just don't want to put a "scary" security settings override for every single Technic Launcher out there; only for the Java versions that really need it.
That's it! Happy gaming.
TL;DR: Newer Java 8 versions (8u351+) no longer support the SHA-1 signatures used by Forge and Big Dig mods, which prevents servers from starting; the Big Dig server packages now include a small Java security override that restores compatibility so they can run on modern Java versions.
Comments