Security |
Documentation Contents |
Security enhancements for the JavaTM 2 SDK, Standard Edition (J2SDK), v 1.4 include the following:Security Guides
- The JavaTM Cryptography Extension (JCE), JavaTM Secure Socket Extension (JSSE), and JavaTM Authentication and Authorization Service (JAAS) security features have now been integrated into the J2SDK, v 1.4 rather than being optional packages.
- There are two new security features:
- The JavaTM GSS-API can be used for securely exchanging messages between communicating applications using the Kerberos V5 mechanism.
- The JavaTM Certification Path API includes new classes and methods in the
java.security.cert
package that allow you to build and validate certification paths (also known as "certificate chains").
- Due to import control restrictions, the JCE jurisdiction policy files shipped with the J2SDK, v 1.4 allow "strong" but limited cryptography to be used. A version of these files indicating no restrictions on cryptographic strengths is available.
- The JSSE implementation provided in this release includes strong cipher suites. However, due to U.S. export control restrictions, this release does not allow alternate "pluggable" SSL/TLS implementations to be used. For more information, please see the JSSE Reference Guide.
- With the integration of JAAS into the J2SDK, the
java.security.Policy
API handles Principal-based queries, and the default policy implementation supports Principal-basedgrant
entries. Thus, access control can now be based not just on what code is running, but also on who is running it.
- Support for dynamic policies has been added. In J2SDK releases prior to version 1.4, classes were statically bound with permissions by querying security policy during class loading. The lifetime of this binding was scoped by the lifetime of the class loader. In version 1.4 this binding is now deferred until needed by a security check. The lifetime of the binding is now scoped by the lifetime of the security policy.
- The graphical Policy Tool utility has been enhanced to enable specifying a Principal field indicating what user is to be granted specified access control permissions.
General SecurityCertification Path JAAS Java GSS-API JCE JSSE
- Security Architecture
- Cryptography Architecture
- How to Implement a Provider for the Java Cryptography Architecture
- Policy Permissions
- Default Policy Implementation and Policy File Syntax
- API for Privileged Blocks
- X.509 Certificates and Certificate Revocation Lists
- Security Managers and the JavaTM 2 SDK
General SecurityCertification Path JAAS
- java.security Package
- java.security.cert Package
- java.security.interfaces Package
- java.security.spec Package
Java GSS-API JCE JSSE
- javax.security.auth Package
- javax.security.auth.callback Package
- javax.security.auth.kerberos Package
- javax.security.auth.login Package
- javax.security.auth.spi Package
- javax.security.auth.x500 Package
- com.sun.security.auth Package
- com.sun.security.auth.callback Package
- com.sun.security.auth.login Package
- com.sun.security.auth.module Package
Located on the Java Software web site:
Copyright © 1995-2002 Sun Microsystems, Inc. All Rights Reserved. Please send comments to: java-security@sun.com. This is not a subscription list. |
Java Software |