Um, So We’ll Have to Lower Java Security Again?
Posted by William Diaz on October 21, 2013
So, last week with the expiration of Java 7 Update 25, Java LiveConnect stopped working on several web sites that our users frequent, forcing them to change the default Java security setting from High to Medium. For arguments sake you could update to Java 7 Update 45 and go back to using the High security setting. But then I saw some additional text on one of the common Java 7 security dialogs: “This application will be blocked in a future Java security update because the JAR file manifest does not contain the Permissions attribute…”
Assuming the applet is not updated by the next JRE expiration, user’s would then have to lower Java security again.