![]() | Documentation Contents |
Signed Applet Upgraded From
.cabto.jarFile Throws a Security Exception When Run in Microsoft Virtual Machine (VM)
SymptomsAfter you upgrade a signed applet from
.cabto.jarfiles, the applet no longer works in the Microsoft VM. The applet runs without any error in the Sun JavaTM Runtime Environment (JRETM) implementation.Cause
Microsoft VM does not support signed
.jarfiles. Microsoft VM supports unsigned.jarfiles through thearchiveattribute of the<APPLET>tag. However Microsoft VM treats classes and resources within the signed.jarfiles as untrusted.As a result, the applet is treated as untrusted by the Microsoft VM. Any action which the applet performs ,that requires access outside the applet sandbox, results in a security exception.
Resolution
The only applet signing scheme recognized by the Microsoft VM is Authenticode technology which is used with the
.cabfiles.Specify the upgraded
.jarfiles through thearchiveattribute for the Sun JRE, and continue to specify the.cabfiles throughcabbasefor the Microsoft VM. For example, assume that you have the following code:
<APPLET code="MyApplet" width=100 height=100>
<PARAM name="cabbase" value="package1.cab, package2.cab">
</APPLET>Change the above code as shown in the following code:
<APPLET code="MyApplet" archive="package1.jar, package2.jar"
width=100 height=100>
<PARAM name="cabbase" value="package1.cab, package2.cab">
</APPLET>Related Information
None.
Copyright © 1993, 2010, Oracle and/or its affiliates. All rights reserved. Please send comments using this Feedback page. |
Java Technology |