IBM WebSphere V5.0 Security - CGISecurity

►
It is also possible to specify additional or different policy file when invoking
execution of an application, using the appropriate command line arguments,
for example:
java -Djava.security.manager -Djava.security.policy=MyPolicyURL
MyApplication
When the policy file is specified using double equals, the specified policy file
will be used exclusively; for example:
-Djava.security.policy==MyOnlyPolicyURL
Security Exceptions
The following exceptions ship with the Java V1.2 SDK:
►
►
java.security.SecurityException
This exception and its subclasses should be runtime exceptions (unchecked,
not declared) that are likely to cause the execution of a program to stop. Such
an exception is thrown when security violation is detected, for example when
trying to access an unauthorized resource.
java.security.GeneralSecurityException
This is a subclass of java.lang.Exception (must be declared or caught) that is
thrown in other cases. Such an exception is thrown when a security-related
(but not vital) problem is detected. For example: passing an invalid key.
Secure class loading
The dynamic class loading is one of the strength of the Java platform, because it
provides the ability to install components at runtime. It is also critical in providing
security because the class loader is responsible for locating and fetching the
class file, consulting the security policy, and defining the class object with the
appropriate permissions.
The java.security.SecureClassLoader is a subclass and an implementation of the
abstract java.lang.ClassLoader class. Other classloaders subclass the
SecureClassLoader to provide different class loading facilities for various
applictions.
Debugging security
Use the -Djava.security.debug=access,failure argument in the virtual machine.
This flag will dump the name of permission checks that are failing.
202 IBM WebSphere V5.0 Security Handbook