Electronic software distribution over networks involves potential security problems. To help address these problems, Netscape Communicator employs a new technology called Object Signing. Object Signing allows users to get reliable information about code they download in much the same way they can get reliable information about shrink-wrapped software. Users can then make informed decisions about downloaded software; for example, whether to allow a signed Java applet to access specific system resources.
Object Signing allows developers to digitally sign any type of file that they may wish to distribute over the Internet. Communicator uses these signed files to determine the privileges granted to Java applets and JavaScript scripts and to authenticate and authorize the automatic installation of Navigator and Composer plug-ins. Communicator 4.01 and later support Netscape Object Signing.
Below is a list of documents and resources that provide information on Object Signing, from creating the Java applet to getting a certificate to packaging and signing it. For additional information, take a look at the Object Signing Datasheet.
When developing Java code, you may wish to bypass the signing stage for much of the development cycle. For information on how to do this, see Security Technote #2: Activating Codebase Principals.
For more information on object-signing certificates, see Object-Signing Tools.