JRE8 update 351 - SHA1 signed applets vs unsigned applets
With the latest JRE8 update we experience an issue with SHA1 signed applets. I realize of course it is not good practise to still use these in the first place.
But in the release notes (https://www.oracle.com/java/technologies/javase/8u351-relnotes.html#JDK-8269039) it is written that they would be treated as being unsinged .
The concerning URL is listed in the expection site list. So with the security exception in place it should work but it doesn't.!? How can we make a temporary exception instead of disabling the new security settings for everyone?