Java Dynamic Management Kit 3.2 Programming Guide
[ Previous ][ Fast Back ]Chapter 14. M-Let, Bootstrap and Launcher Services[ Fast Forward ][ Next ]

Code Signing

The m-let and bootstrap services support signed .jar files. In the code signing environment, this involves:

On the agent side, code signing involves the following:

Example

Example 14-14 shows a policy file entry for a jar file named example.jar coming from an HTTP server with codebase http://java.sun.com/ and signed by tester. This entry grants two permissions, the first one grants read access to all files in the directory /tmp and the second one grants access to the objects registered in the framework.

Example 14-14. Example Policy File Entry
grant codeBase "http://java.sun.com/example.jar", signedBy "tester" {
   permission java.io.FilePermission "/tmp/*", "read";
   permission com.sun.jaw.reference.agent.cmf.FrameworkPermission "accessObjects";
};


[ Previous ][ Home ][ Next ]
Security Manager[ Up ]Launcher Service