Hi again,

Java 7 update 25 (Java 6 update 51) introduced a new manifest file attribute: Permissions. If an applet needs privileges outside the sandbox (like accesing MSCAPI), the manifest file should have this new attribute with value "all-permissions".

In is not mandatory yet, but trying to execute an applet with privileges, but without Permissions attribute in its manifest, result in a warning message. That warning (and release documentation), states that user can allow execution of the applet, but that in the future, that possibility will be removed, and applets without Permissions attribute will be blocked without asking.

Since it is becoming common practice for browsers to block applets unless last JRE version is installed, and new JREs could block applets without Permissions attribute, it is very desirable to include a Permissions attribute in the manifest file, for new JCAPI versions. A new JRE release could ruin every application using current JCAPI version.

Regards,

Alfonso.

Hi Alfonso,

Thanks for the information.
We're about to release a new version of JCAPI containing one bug fix. It will also be re-signed with new code signing certificates from Oracle and DigiCert. We'll investigate this new Permissions feature/constraint and make sure that it will be part of the next release as well.

Regards,
Tommy

Hi,

The reported problem has now been fixed in JCAPI version 1.2.8 and 2.2.1.

Regards,
Tommy