Local file reading by signed applets blocked by MacOS

[Joshua Smith]

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 use the "m" option to jar when I create the jar to put this into the manifest:

Codebase: *
Application-Name: { my application name }
Permissions: all-permissions

-Joshua

On Nov 13, 2013, at 2:14 PM, Mickey Segal <java3 at segal.org> wrote:

> 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 update 45 since it also occurs with Update 40, and that had been working fine until a week or two ago, as assessed by reports from users of a large applet.  The demo applet was prepared to demo the problem using concise code.  
> 
> 
> 
> A signed applet is supposed to be able to read and write local files.  Although this capability is restricted on some institutional networks, this is the first time these abilities have been restricted for individual users.
> 
> 
> 
> Does anyone know whether this is a bug, or done purposely by Apple?
> 
> 
> 
> Are there any workarounds of settings that a user can set to allow such file reading?
> 
> 
> 
> Since this appears to represent a change by Apple, should this be reported as an Apple bug, an Oracle Java bug, or both? 
>