On 5/21/2013 8:45 AM, Knute Johnson wrote:
I've got some software running in the wild that uses JApplets. My
client decided to update the Java version from 1.6 something to
1.7.0_21. The applets communicate with the server they come from. This
caused a security exception. I re-compiled and self-signed one of the
applets to see if that would solve the issue but then I got a
ConnectException. I'm not sure why and it could be related to the
Serialzed data being transmitted between the applet and server.
Should self signing the .jar files solve any problems from changing the
Java versions for my applets?
I just found this on the Oracle site;
"Changes to Java Control Panel's Security Settings
In this release, low and custom settings are removed from the Java
Control Panel(JCP)'s Security Slider.
Depending on the security level set in the Java Control Panel and the
user's version of the JRE, self-signed or unsigned applications might
not be allowed to run. The default setting of High permits all but local
applets to run on a secure JRE. If the user is running an insecure JRE,
only applications that are signed with a certificate issued by a
recognized certificate authority are allowed to run."
What do they mean by a secure JRE?
And with recent history secure approx. means latest.