Java Dynamic Management Kit 3.2 Programming Guide
[ Previous ][ Fast Back ]Chapter 11. Security[ Fast Forward ][ Next ]

Security in Class Loading Services

Class and Library Loading Services

The class and library server serves classes and libraries to the class loader and the library loader. An agent uses the class loader to obtain new classes from an arbitrary location. The library loader loads native libraries into the framework. The operation of the class loading services is described fully in Chapter 13.

When provided with a code signing directive file (see Code Signing Directive File in Chapter 13), and the signer's public and private keys, the class and library server is capable of signing code. The directive file and keys must be provided when the class and library server is started. The class loader must have access to the signer's certificate, that is, the signer's certificate must be stored in the keystore on the machine on which the agent is running. For more details, see Chapter 13.

M-let and Bootstrap Services

The m-let and bootstrap services are able to load .jar files that have been signed using the jarsigner utility provided with JavaŽ 2 SDK, Standard Edition, version 1.2. In the same way as the class and library server, the machine where the agent is running must have the signer's certificate in its keystore. Otherwise, the service will be unable to load .jar files signed by that signer. For more details, see Chapter 14.


[ Previous ][ Home ][ Next ]
Extended Permissions[ Up ]Permissions File