Article ID: 305830 - View products that this article applies to.
This article was previously published under Q305830
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/256986/EN-US/ )Description of the Microsoft Windows Registry
When you are using the Microsoft Java Virtual Machine version 5.00.3802, the disabling of unsigned applets also appears to disable signed applets.
This behavior can occur because to fix a security vulnerability, it is necessary to give unsigned applets the right to connect to the originating server for any code to run, as before the cab or class file has been downloaded, it is not known what permissions the applet will have. The security vulnerability is described in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/253562/EN-US/ )FIX: Untrusted Code Can Access Files on End-User Systems
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To alter this behavior, use either of the following methods.
To Allow All Unsigned Applets
To Allow Unsigned Applets Only the Right to Connect Back to the Originating Server
When you allow unsigned applets the right to connect back to the originating server, they have basic rights to run simple applets which are unable to read from the file system or from the registry.
Article ID: 305830 - Last Review: January 31, 2007 - Revision: 3.2