Thanks for the clarification. The "Run in Unsafe Mode" language, however, is a
bit extreme for a situation in which a user has already accepted a digital
certificate. Something along the lines of "Trust the digital certificate I
already trusted" would seem more accurate. However, even that re
I found a further problem and a workaround to both problems.
The workaround is to use Firefox, which does not suffer from the problem
described below. So it seems that a recent Safari update must be the problem.
In addition, the ability of a signed applet to use Runtime.getRuntime().exec to
In Safari, you now have to explicitly drop the OS sandbox put around the Java
process, per site:
Safari > Preferences > Security > Manage Website Settings… > Java > (your site)
> Run in Unsafe Mode
Regards,
Mike Swingler
Apple Inc.
On Nov 13, 2013, at 12:50 PM, Mickey Segal wrote:
> I’ve als
I’ve also demonstrated that the same problem affects a signed Java applet
trying to write files on the Macintosh. The write-up is at
http://www.segal.org/java/localFileWrite/. Each write-up references the other
so as to give a more complete version of the problem.
Feedback would be appreci
Did you include permissions in your Manifest?
It used to be that signing an applet was sufficient to get read permissions,
but Oracle recently added the requirement that you explicitly list the
permissions you want.
I am using a signed applet for uploading files, and not having any problems.
I
A change in MacOS in the past week or two appears to have blocked local file
reading by signed Java applets running Java 7. I’ve illustrated the problem
with a working example and full source code at
http://www.segal.org/java/localFileRead/. The problem does not seem to be
related to Java 7 u
