Local file reading by signed applets blocked by MacOS

[Mickey Segal]

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 reminds me of the security warning overreaction in Windows Vista, in which one constantly got dialog boxes of "do you want to do what you just asked to do".  Subsequent versions of Windows took a more Apple-like approach to security, but it sounds like Apple is now taking a Vista-like approach here.

We'll modify our warning about the Macintosh problems affecting our software to include this workaround, but due to one other Safari bug (http://www.segal.org/java/Hello/) and one other Macintosh Java problem that Oracle is blaming on Apple (http://www.segal.org/java/refresh4/), we already have a special warning on our software for Macintosh users leading to a list of problems to be worked around.

Mike Swingler [mailto:swingler at apple.com] wrote: 
Sent: Wednesday, November 13, 2013 4:10 PM

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.