# IBM Security Guide

# IBM SDK for Solaris, Java 2 Technology Edition, Version 5.0
HP JDK for J2SE HP-UX 11i, adapted by IBM for IBM software, Version 5.0

# Copyright information

Note: Before using this information and the product it supports, read the general information under Notices.

This edition of the User Guide applies to:

- iKeyman
- IBM Java(TM) Certification Path (CertPath) v1.0 Provider
- IBM(R) Java Cryptography Extension (JCE) Provider
- |IBM Java Generic Security Service (JGSS) v1.5 |Provider
- |IBM Java Secure Socket Extension (JSSE) IBM JSSE2 Provider
- IBM PKCS11 Implementation Provider
- IBM Java JCE FIPS Provider
- |IBM SASL Provider v1.5
- |Key Certificate Management utilities

and to all subsequent releases and modifications until otherwise indicated in new editions.

(c) Copyright Sun Microsystems, Inc. 1997, 2004, 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.

(c) Copyright International Business Machines Corporation, 1999, 2007. All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

# Preface

The security components described in this User Guide are shipped with the SDK and are not extensions. They provide a wide range of security services through standard Java(TM) APIs (except iKeyman). The security components contain the IBM(R) implementation of various security algorithms and mechanisms. IBM does not provide support for any of the IBM Java security components when used with a non-IBM JVM or with non-IBM security providers when used with the IBM JVM.

|The IBM SDK also provides a FIPS 140-2 certified cryptographic |module, IBMJCEFIPS, implemented as a JCE provider. Applications can comply |with the FIPS 140-2 requirements by using the IBMJCEFIPS module.

The CertPath component provides PKIX-compliant certification path building and validation.

The JGSS component provides a generic API that can be plugged in by different security mechanisms. IBM JGSS uses Kerberos V5 as the default mechanism for authentication and secure communication.

The JCE framework has two providers: IBMJCE is the pre-registered default provider; IBMJCEFIPS is optional.

|JSSE is the Java implementation of the SSL and TLS protocols. |The JSSE pre-registered default provider is IBMJSSE2.

|IBM Java Simple Authentication and Security Layer, or |SASL, is an Internet standard (RFC 2222) that specifies a protocol for authentication |and optional establishment of a security layer between client and server applications.

The Java security configuration file does not refer to the Sun provider. The IBM JCE provider has replaced the Sun provider. The JCE supplies all the signature handling message digest algorithms that were previously supplied by the Sun provider. It also supplies the IBM secure random number generator, IBMSecureRandom, which is a real Random Number Generator. SHA1PRNG is a Pseudo Random Number Generator and is supplied for code compatibility. SHA1PRNG is not guaranteed to produce the same output as the SUN SHA1PRNG.

In the IBM SDK v1.4.1, the following options were added to the java.security.debug property to help you debug Java Cryptography Architecture (JCA)-related problems:

- provider - displays each provider request and load, provider add and provider remove. It also displays the related exception when a provider load fails.
- algorithm - displays each algorithm request, which provider has supplied the algorithm and the implementing class name.
- :stack - you can append this option to either of algorithm - or provider. When you request an algorithm, a stack trace is displayed. Use this stack trace to determine the code that has requested the algorithm. This option also prints the stack trace for exceptions that are swallowed or converted.
- :thread - adds the thread id to all debug message lines. You can use this option together with all the other debug options.

An example of a valid option string is "provider, algorithm:stack".

In this guide, you'll see a 'What's new' section for each component. This information is provided to help you with migration.

# Contents

Copyright information
Preface
General information about IBM security providers
Java Certification Path (CertPath)
Differences between IBM and Sun versions of CertPath
What's new?
Documentation
Java Cryptography Extension (JCE)
Differences between IBM and Sun versions of JCE
What's new?
Documentation
Java Generic Security Service (JGSS)
Differences between IBM and Sun versions of JGSS
What's new?
Documentation
IBMJSSE2 Provider
| |
Differences between the IBMJSSE Provider and the IBMJSSE2 Provider
Differences between the IBMJSSE2 Provider and Sun's version of JSSE
What's new?
Documentation
IBMPKCS11Impl Provider
Differences between IBM and Sun versions of IBMPKCS11Impl
What's new?
Documentation
IBMJCEFIPS Provider
Differences between IBM and Sun versions of IBMJCEFIPS
What's new?
Documentation
| |
IBM SASL Provider
| |
Differences between Sun and IBM SASL Provider
| |
What's new
| |
Documentation
| |
Key Certificate Management utilities
| |
What's new
| |
Documentation
Notices
Trademarks

# General information about IBM security providers

The IBM SDK v5.0 has been tested with the following default security providers:

| |
- security.provider.1=com.ibm.security.jgss.IBMJGSSProvider
|
- security.provider.2=sun.security.provider.Sun
|
- security.provider.3=com.ibm.crypto.provider.IBMJCE
|
- security.provider.4=com.ibm.jsse2.IBMJSSEProvider2
|
- security.provider.5=com.ibm.security.cert.IBMCertPath
|
- security.provider.6=com.ibm.security.sasl.IBMSASL

You can add other IBM security providers either statically or from within your Java application's code. To add a new provider statically, edit a java security properties file (for example, java.security). To add a new provider from your application's code, use the methods of the java.security.Security class (for example, `java.security.Security.addProvider()`).

You can also add this IBM security provider, com.ibm.crypto.fips.provider.IBMJCEFIPS.

Note that code written for the IBMJSSE Provider might not compile or execute in exactly the same way for IBMJSSE2. For details, see IBMJSSE2 Provider.

# Java Certification Path (CertPath)

The Java Certification Path API provides interfaces and abstract classes for creating, building, and validating certification paths (also known as "certificate chains").

## Differences between IBM and Sun versions of CertPath

The IBM CertPath classes differ from the Sun version in the following ways:

- The IBM CertPath provider is in the package com.ibm.security.cert.
- The IBM CertPath provider is called "IBMCertPath". Sun does not have a separate provider for CertPath; CertPath is already supported by the "SUN" provider.
- To enable CRL Distribution Points extension checking, use the system property com.ibm.security.enableCRLDP. The system property used by the Sun version is com.sun.security.enableCRLDP.
- When checking the certificate's CRL Distribution Points extension, Sun's version retrieves the CRL only if the CRL location is specified as an HTTP URL value inside the extension. The IBM provider recognizes both HTTP and LDAP URLs.

## What's new?

|The following changes have been added in v5.0:

| |
- Support of checking a certificate's revocation status based on On-Line |Certificate Status Protocol (OCSP) has been added.
|
- A new constructor and a public API in TrustAnchor class have been added: |
  |
  - `public TrustAnchor(X500Principal caPrincipal, PublicKey pubKey, byte[] |nameConstraints);`
  |
  - `public final X500Principal getCA();`
|
- Four new public APIs in X509CertSelector have been added: |
  |
  - `public X500Principal getIssuer();`
  |
  - `public void setIssuer(X500Principal issuer);`
  |
  - `public X500Principal getSubject();`
  |
  - `public void setSubject(X500Principal subject);`
|
- Three new public APIs in X509CRLSelector have been added: |
  |
  - `public void setIssuers(Collection issuers);`
  |
  - `public void addIssuer(X500Principal issuer);`
  |
  - `public Collection getIssuers();`
|
- The PolicyQualifier class has been changed to be non-final and its public |APIs have changed to be final.

The following changes were added in v1.4.2:

- The performance of the IBM CertPath provider has been improved.
- Limited support for the CRL Distribution Points extension has been added.
- IBM LDAP CertStore provides caching to cache lookups.

The following changes were added in v1.4.1:

- The trusted certificate that acts as TrustAnchor can be an X.509 v1 certificate.
- When you specify the certificate's subject or issuer name as a String in X509CertSelector, the search for a matched certificate mechanism checks only the name value and ignores the tag type.

There were no changes in v1.4.1 over v1.4.0.

The following changes were added in v1.4.0:

- Certificates from CertificatePair entry can be retrieved from LDAP type certstore.
- The framework package name was changed from javax.security.cert to java.security.cert. However, the old framework package is still supported.

## Documentation

For detailed information, including API documentation and samples, see the developerWorks Web site, at http://www.ibm.com/developerworks/java/jdk/security/index.html.

# Java Cryptography Extension (JCE)

The Java Cryptography Extension (JCE) provides a framework and implementations for encryption, key generation and key agreement, and Message Authentication Code (MAC) algorithms. Support for encryption includes symmetric, asymmetric, block, and stream ciphers. The software also supports secure streams and sealed objects. JCE supplements the Java 2 platform, which already includes interfaces and implementations of message digests and digital signatures.

You can obtain unrestricted jurisdiction policy files from http://www.ibm.com/developerworks/java/jdk/security/index.html.

|The v1.4.2 unrestricted (and restricted) jurisdiction policy |files are suitable for use with v5.0. The v1.4.1 files are not suitable.

## Differences between IBM and Sun versions of JCE

The com.sun.* packages are reimplemented by IBM and renamed com.ibm.* packages.

The IBM version of JCE differs from the Sun version in the following ways:

- The com.sun.crypto.* packages are reimplemented by IBM and renamed com.ibm.crypto.* packages.
- The IBM JCE provider replaces the Sun providers sun.security.provider.Sun, com.sun.rsajca.Provider, and com.sun.crypto.provider.SunJCE.
- IBM provides more algorithms than Sun does:
  - Cipher algorithms
    - AES
    - Blowfish
    - DES
    - Mars
    - |ARCFOUR
    - PBE with MD2 and DES
    - PBE with MD2 and Triple DES
    - PBE with MD2 and RC2
    - PBE with MD5 and DES
    - PBE with MD5 and Triple DES
    - PBE with MD5 and RC2
    - PBE with SHA1 and DES
    - PBE with SHA1 and TripleDES
    - PBE with SHA1 and RC2
    - PBE with SHA1 and 40-bit RC2
    - PBE with SHA1 and 128-bit RC2
    - PBE with SHA1 and 40-bit RC4
    - PBE with SHA1 and 128-bit RC4
    - PBE with SHA1 and 2-key Triple DES
    - PBE with SHA1 and 3-key Triple DES
    - RC2
    - RC4
    - RSA encryption/decryption
    - |RSA encryption/decryption with OAEP Padding
    - Seal
    - Triple DES
  - Signature algorithms
    - |SHA1 with RSA, SHA2 with RSA, SHA3 with RSA, SHA5 with RSA, |MD5 with RSA, MD2 with RSA signatures
    - SHA1 with DSA signature
  - Message digest algorithms
    - SHA1
    - SHA2
    - SHA3
    - SHA5
    - MD5
    - MD2
  - Message authentication code (MAC)
    - Hmac/SHA1
    - Hmac/MD5
    - |Hmac/SHA2
    - |Hmac/SHA3
    - |Hmac/SHA5
  - Key agreement algorithm
    - DiffieHellman
  - Random number generation algorithms
    - IBMSecureRandom
    - IBM SHA1PRNG
  - Key Store
    - JCEKS
    - JKS
    - PKCS12KS

## What's new?

|The following changes are made in v5.0:

| |
- RSA with OAEP Padding is added
|
- SHA2withRSA, SHA3withRSA and SHA5withRSA signature algorithms are added
|
- HmacSHA2, HmacSHA3, HmacSH5 MAC algorithms are added.
|
- ARCFOUR encryption algorithm is added

The following changes were made in v1.4.2:

- SHA2, SHA3 and SHA5 algorithms were added for hashing
- SHA1PRNG algorithm was added for generating pseudo random numbers

There were no changes in v1.4.1 from v1.4.0.

The following changes were made in v1.4.0:

- AES cipher algorithm has been added.
- Strong cryptography is the default, unlimited cryptography is available.
- Provider authentication of the JCE framework no longer required.
- JCE is now shipped with the Java SDK v1.4 on all platforms.

## Documentation

For detailed information, including API documentation and samples, see the developerWorks Web site at http://www.ibm.com/developerworks/java/jdk/security/index.html.

# Java Generic Security Service (JGSS)

The Java Generic Security Service (JGSS) API provides secure exchange of messages between communicating applications.

The JGSS is an API framework that has Kerberos V5 as the underlying default security mechanism. The API is a standardized abstract interface under which you can plug different security mechanisms that are based on private-key, public-key, and other security technologies. JGSS shields secure applications from the complexities and peculiarities of the different underlying security mechanisms. JGSS provides identity and message origin authentication, message integrity, and message confidentiality. JGSS also features an optional Java Authentication and Authorization Service (JAAS) Kerberos login interface, and authorization checks. JAAS augments the access control features of Java 2, which is based on CodeSource with access controls based on authenticated principal identities.

## Differences between IBM and Sun versions of JGSS

The IBM version of JGSS differs from the Sun version in the following ways:

- The com.sun.* packages are reimplemented by IBM and renamed com.ibm.* packages.
- The format of the parameters passed to the Java tools kinit, ktab, and klist is different from Sun's equivalent tools.

## What's new?

|The following change is added in v5.0 Service Refresh 1:

| |
AES is now a supported algorithm type
|
  These additional algorthims can be set in the krb5.conf file under [libdefault] |as follows: |
  default_tkt_enctypes = aes128-cts-hmac-sha1-96
  |default_tkt_enctypes = aes256-cts-hmac-sha1-96
  |default_tgs_enctypes = aes128-cts-hmac-sha1-96
  |default_tgs_enctypes = aes256-cts-hmac-sha1-96
  |
  |default_checksum = hmac-sha1-96-aes128
  |default_checksum = hmac-sha1-96-aes256
  |
  |

|The following changes are added in v5.0:

| |
TCP or UDP Preference Configuration
|
  J2SE now supports the use of the udp_preference_limit property in the Kerberos configuration file (krb5.ini). When sending |a message to the KDC, the J2SE Kerberos library will use TCP if the size of |the message is above udp_preference_list. If the message |is smaller than udp_preference_list, UDP will be tried |up to three times. If the KDC indicates that the request is too big, the J2SE |Kerberos library will use TCP. |
|
IPv6 support in Kerberos
|
  J2SE now supports IPv6 addresses in Kerberos tickets. Before J2SE 5, |only IPv4 addresses were supported in tickets. |
|
TGT Renewals
|
  The Java Authentication and Authorization Server (JAAS) Kerberos login |module in v5.0, Krb5LoginModule, now supports Ticket Granting Ticket (TGT) |renewal. This support allows long-running services to renew their TGTs automatically |without user interaction or requiring the services to restart. With this |feature, if Krb5LoginModule obtains an expired ticket from the ticket cache, |the TGT will be automatically renewed and be added to the Subject of the caller |who requested the ticket. If the ticket cannot be renewed for any reason, |Krb5LoginModule will use its configured callback handler to retrieve a username |and password to acquire a new TGT. |

  To use this feature, configure Krb5LoginModule |to use the ticket cache and set the newly introduced renewTGT option to true. Here is an example of a JAAS login configuration file |that requests TGT renewal:

  |

      server {
      |  com.ibm.security.auth.module.Krb5LoginModule required
      |        principal=principal@your_realm
      |		useDefaultCcache=TRUE
      |		 renewTGT=true;
      |};

  Note that if renewTGT is set to true, useDefaultCcache must also be set to true; otherwise, it results in a |configuration error. |

The following changes were added in v1.4.2:

Configurable Kerberos Settings
  You can provide the name and realm settings for the Kerberos Key Distribution Center (KDC) either from the Kerberos configuration file or by using the system properties files java.security.krb5.kdc and java.security.krb5.realm. You can also specify the boolean option refreshKrb5Config in the entry for Krb5LoginModule in the JAAS configuration file. If you set this option to `true`, the configuration values will be refreshed before the login method of the Krb5LoginModule is called.
Support for Slave Kerberos Key Distribution Center
  Kerberos uses slave KDCs so that, if the master KDC is unavailable, the slave KDCs will respond to your requests. In previous releases, Kerberos tried the master KDC only and would give up if there was no response within the default KDC timeout.
Support TCP for Kerberos Key Distribution Center Transport
  Kerberos uses UDP transport for ticket requests. In cases where Kerberos tickets exceed the UDP packet size limit, Kerberos supports automatic fallback to TCP. If a Kerberos ticket request using UDP fails and the KDC returns the error code `KRB_ERR_RESPONSE_TOO_BIG`, TCP becomes the transport protocol.
Kerberos Service Ticket in the Subject's Private Credentials
  The Kerberos service ticket is stored in the Subject's private credentials. This gives you access to the service ticket so that you can use it outside the JGSS (for example, in native applications or for proprietary uses). In addition, you can reuse the service ticket if the application tries to establish a security context to the same service again. The service ticket should be valid for it to be reusable.

The following change was added in v1.4.1:

- Wrappers have been added for the klist, kinit, and ktab Java tools. These wrappers invoke the relevant tool classes so that you do not have to remember the full package name.

## Documentation

For detailed information about JGSS, including API documentation and samples, see the developerWorks Web site, at http://www.ibm.com/developerworks/java/jdk/security/index.html.

# IBMJSSE2 Provider

|The Java Secure Socket Extension (JSSE) is a Java package that |enables secure internet communications. It implements a Java version of SSL |(Secure Sockets Layer) and TLS (Transport Layer Security) protocols and includes |functions for data encryption, server authentication, message integrity, and |optional client authentication.

|By abstracting the complex underlying security algorithms and |"handshaking" mechanisms, JSSE minimizes the risk of creating subtle but dangerous |security vulnerabilities. Also, it simplifies application development by serving |as a building block that you can integrate directly into your applications. |Using JSSE, you can provide for the secure passage of data between a client |and a server running any application protocol (such as HTTP, Telnet, NNTP, |and FTP) over TCP/IP.

|Because Solaris and HP-UX systems use |a JVM provided by Sun, you must explicitly set the HTTPS protocol handler |to the IBM handler, which is com.ibm.net.ssl.www2.protocol.Handler. If you do not set the HTTPS protocol handler, the JVM attempts to use |Sun's HTTPS handler, which does not exist. In this case, SSL connections |will fail.

|In v5.0, the IBMJSSE2 Provider, which was introduced in the |v1.4.2 JVM, has replaced the IBMJSSE Provider. Although they are nearly equivalent, |there are differences between the two providers. See the next section for |details.

| | |

## Differences between the IBMJSSE Provider and the IBMJSSE2 Provider

|

The now-discontinued IBMJSSE Provider and the IBMJSSE2 Provider differ |in the following ways:

|

|
- The IBMJSSE2 Provider is called "com.ibm.jsse2.IBMJSSEProvider2". |
|
|
- The HTTPS protocol handler for the IBMJSSE2 Provider is called "com.ibm.net.ssl.www2.protocol.Handler". | The "com.ibm.net.ssl.internal.www.protocol.Handler" and the "com.ibm.net.ssl.www.protocol.Handler" |protocol handlers have been removed. |
|
|
- The IBMJSSE2 Provider does not support the com.ibm.net.ssl framework. |Use the javax.net.ssl framework instead. |
|
|
- The IBMJSSE2 Provider does not support the SSL version 2 protocol. However, |the server side of a JSSE2 connection does accept the "SSLv2Hello" protocol. | |
|
|
- The AES_256 ciphers require the installation of the JCE Unlimited Strength |Jurisdiction Policy. The old IBMJSSE Provider did not use JCE for its cryptographic |support and therefore did not require these files. |
|
|
- The IBMJSSE2 Provider requires a JCE Provider for its cryptography. |
|
|
- | The IBMJSSE2 Provider does not build the server's private |key certificate chain from the trusted keystore. The trusted certificates |must be added to the server's private key to complete the chain. This is an |incompatible change. |
  |
|
|
- The IBMJSSE2 Provider considers a certificate trusted if you have the |private key. |
|
|
- The HTTPS protocol handler for the IBMJSSE2 Provider performs hostname |verification and rejects requests where the host to connect to and the server |name from the certificate do not match. A HostnameVerification implementation |called "com.ibm.jsse2.HostnameVerifierIgnore" is provided. "com.ibm.jsse2.HostnameVerifierIgnore" |always accepts the connection even when a mismatch occurs. |
|
|
- Tracing no longer requires a separate debug jar. |
|
|
- The class com.ibm.jsse.SSLContext which in IBMJSSE is used to access secure |tokens has been removed. Use the hardware crypto support in IBMJSSE2 instead. | See the documentation on the developerWorks Web site http://www.ibm.com/developerworks/java/jdk/security/index.html for details. |
|
|
- The IBMJSSEFIPS Provider has been removed. JSSE FIPS support is supported |within the IBMJSSE2 Provider and no separate jar is required. See the documentation |on the developerWorks Web site http://www.ibm.com/developerworks/java/jdk/security/index.html for instructions how to set up JSSE to run in FIPS mode. |

## Differences between the IBMJSSE2 Provider and Sun's version of JSSE

The IBMJSSE2 Provider differs from the Sun JSSE in the following ways:

- The IBM JSSE Provider is called "com.ibm.jsse2.IBMJSSEProvider2".
- The IBM KeyManagerFactory is called "IbmX509".
- The IBM TrustManagerFactory is called "IbmX509" or "IbmPKIX".
- |The IBM HTTPS protocol handler is called "com.ibm.net.ssl.www2.protocol.Handler". |
- IBMJSSE2 does not support the com.sun.net.ssl framework; use the javax.net.ssl framework instead.
- You can use PKIK revocation checking by setting the system property com.ibm.jsse2.checkRevocation to "true".
- The IBM implementation supports the following protocols for the engine class SSLContext, for the api setEnabledProtocols in the SSLSocket, and for SSLServerSocket classes:
  - SSL
  - SSLv3
  - TLS
  - TLSv1
  - SSL_TLS
  The IBM implementation does not support the "SSLv2Hello" protocol. The IBM implementation supports the SSL v2 protocol. You can use the IBM SSLContext getInstance() factory method to control which protocols are enabled for an SSL connection. Using SSLContext's getInstance() or the setEnabledProtocols() methods provides the same result. With Sun's JSSE, the protocol is controlled through setEnabledProtocols().
- IBM and Sun support different cipher suites.
- The IBM JSSE TrustManager does not allow anonymous ciphers. To handshake with an anonymous cipher, a custom TrustManager that allows anonymous ciphers must be provided.
- When a null KeyManager is passed to SSLContext, the IBM JSSE KeyManagerFactory implemention will check system properties, then jssecacerts, if it exists, and finally uses the cacerts file to find the key material. Sun's JSSE creates an empty KeyManager.
- The IBM JSSE X509TrustManager and X509KeyManager throws an exception if the TrustStore or KeyStore specified by the system properties does not exist, if the password is incorrect, or if the keystore type is inappropriate for the actual keystore. Sun's X509TrustManager creates a default TrustManager or KeyManager with an empty keystore.
- The IBM JSSE implementation verifies the entire server or client certificate chain, including trusted certificates. For example, if a trusted certificate has expired, the handshake fails, even though the expired certificate is trusted. Sun's JSSE verifies the certificate chain up to the trusted certificate. Verification stops when it reaches a trusted certificate and the trusted certificate and beyond are not verified.
- The IBM JSSE implementation returns the same set of supported ciphers for the methods getDefaultCiphersSuites and getSupportedCipherSuites. Sun's JSSE getDefaultCipherSuites returns the list of cipher suites that provide confidentiality protection and server authentication (that is, no anonymous cipher suites). Sun's getEnabledCipherSuites returns the entire list of cipher suites that Sun supports.
- For Sun's implementation, DSA server certificates can use only *_DH*_* cipher suites. For the IBM implementation, if the server has a DSA certificate only and only RSA* ciphers are enabled, the connection succeeds with an RSA cipher. DSA will be used for authentication and ephemeral RSA will be used for the key exchange.
- |To use a hardware keystore or truststore with IBM's hardware |crypto provider by means of system properties, set the javax.net.ssl.keyStoreType and javax.net.ssl.trustStoreType system properties, |respectively, to "PKCS11IMPLKS". For the Sun implementation, the system property |is set to "PKCS11". |
- |The IBM JSSE Provider can be enabled to run in FIPS mode. | The Sun JSSE cannot.

## What's new?

|The following change takes effect from v5.0 Service Refresh |5:

| |
- When IBMJSSE2 is used as a server, if the SSLv3 protocol is to be used |for the handshake, it will no longer agree to use any of the AES cipher suites. | Previously, the selection of the cipher suite was independent of the protocol |selected so you could do an old-style SSLv3 handshake with a more modern AES |cipher suite. The TLS protocol is not affected by this change. This change |was required to support Microsoft Vista clients.

|The following changes have been added in v5.0

| |
- The IBMJSSE Provider is removed for v5.0. Use the IBMJSSE2 Provider instead. |
|
|
- The IBMJSSE2 implementation now uses the Java Cryptography Extension (JCE) |for all its cryptographic algorithms. In v1.4.2, only the IBMJCE providers |were supported. |
|
|
- The IBMJSSE2 implementation now supports any hardware crypto provider. | This support will require applications that ran in v1.4.2 using the IBMPKCS11Impl |provider to use a configuration file in order to run successfully. |
|
|
- SSLEngine (non-blocking I/O) allows SSL/TLS applications to choose their |own I/O and compute models. |
|
|
- Enhanced TrustManager support HTTP/HTTPS enhancements. |
|
|
- New and updated Methods and Classes. |
|
|
- Kerberos cipher suites are available, if supported by the operating system. |

The IBMJSSE2 Provider was new for v1.4.2.

## Documentation

For detailed information, including API documentation and samples, see http://www.ibm.com/developerworks/java/jdk/security/index.html.

# IBMPKCS11Impl Provider

|The IBMPKCS11Impl Provider is not supported |on the HP-UX 11i.

The IBMPKCS11Impl Provider uses the Java Cryptography Extension (JCE) and Java Cryptography Architecture (JCA) frameworks to add the ability to use hardware cryptography through the Public Key Cryptographic Standards #11 (PKCS #11) standard. This provider takes advantage of hardware cryptography within the existing JCE architecture and gives Java programmers the significant security and performance advantages of hardware cryptography with minimal changes to existing Java applications. Because the complexities of hardware cryptography are handled within the normal JCE, advanced security and performance using hardware cryptographic devices is available readily.

PKCS#11 is a standard that provides a common application interface to cryptographic services on various platforms through several hardware cryptographic devices. See the IBMPKCS11Impl provider user guide for a list of supported devices.

## Differences between IBM and Sun versions of IBMPKCS11Impl

|The most significant difference between the SunPKCS11 provider |and the IBM PKCS11Impl provider is in the area of keystore. Sun has a keystore |named PKCS11 and IBM has one called IBMPKCS11KS. Sun requires that all trusted |certificates have the attribute CKA_TRUSTED set to true. |The IBM keystore assumes that any certificates on the device are trusted. |So, this assumption should allow IBM's keystore to work with data that was |saved using the Sun PKCS11 provider keystore, but not the other way around.

## What's new?

|The following changes were made in v5.0.

|IBMPKCS11Impl has been updated to allow more algorithms and |to allow the Sun 5.0 methods of initialization of the provider. The new algorithms |are:

| |
- AES
|
- Diffie-Hellman
|
- RC4, also known as ArcFour
|
- Blowfish
|
- SHA-256
|
- SHA-384
|
- SHA-512
|
- SHA256withRSA
|
- SHA384withRSA
|
- SHA512withRSA
|
- HmacMD5
|
- HmacSHA1
|
- HmacSHA256
|
- HmacSHA384
|
- HmacSHA512

|In v5.0, the ability to pass in a configuration file to the |provider is added. This configuration file can contain a significant amount |of information about the device; for example, what it should or should not |do. After the provider is created, the application can log in to the card |in different ways. Some devices allow you to perform some cryptographic functions |without logging into the device. The v1.4.2 ways to initialize the device |still work. However, you can no longer have more than one of these providers |at a time. Instead, with this release, you can initialize more than one IBMPKCS11Impl |provider using the 5.0 configuration file and login methods.

|The classes DESPKCS11KeyParameterSpec and DESedePKCS11KeyParameterSpec |have been deprecated. Use the GeneralPKCS11KeyParameterSpec class for all |symmetric key types (for instance, DES, DESede, AES, RC4, Blowfish).

The IBMPKCS11Impl Provider was new for v1.4.2.

## Documentation

For detailed information, including API documentation, see the developerWorks Web site at http://www.ibm.com/developerworks/java/jdk/security/index.html.

# IBMJCEFIPS Provider

The IBM Java JCE (Java Cryptographic Extension) FIPS Provider (IBMJCEFIPS) for multi-platforms is a scalable, multi-purpose cryptographic module that supports FIPS-approved cryptographic operations through Java APIs. The IBMJCEFIPS includes the following Federal Information Processing Standards (FIPS) 140-2 [Level 1] compliant components:

- IBMJCEFIPS for Solaris,
- IBMJCEFIPS for HP
- IBMJCEFIPS for Windows
- IBMJCEFIPS for z/OS
- IBMJCEFIPS for AS/400
- IBMJCEFIPS for Linux (Red Hat and SUSE)

To meet the requirements specified in the FIPS publication 140-2, the encryption algorithms used by the IBMJCEFIPS Provider are isolated into the IBMJCEFIPS Provider cryptographic module, which you can access using the product code from the Java JCE framework APIs. Because the IBMJCEFIPS Provider uses the cryptographic module in an approved manner, the product complies with the FIPS 140-2 requirements.

Type | Algorithm | Specification
--- | --- | ---
Symmetric Cipher | AES (ECB, CBC, OFB, CFB and PCBC) | FIPS 197
Symmetric Cipher | Triple DES (ECB, CBC, OFB, CFB and PCBC) | FIPS 46-3
Message Digest | |SHA1 |SHA-256 |SHA-384 |SHA-512 |HMAC-SHA1 | |FIPS 180-2 | | | |FIPS 198a
Random Number Generator | FIPS 186-2 Appendix 3.1 | FIPS 186-2
Digital Signature | DSA (512 - 1024) | FIPS 186-2
Digital Signature | RSA (512 - 2048) | FIPS 186-2

In addition, the IBMJCEFIPS supports the following unapproved algorithms:

Type | Algorithm | Specification
--- | --- | ---
Asymmetric Cipher | RSA | PKCS#1
Key Agreement | Diffie-Hellman | PKCS #3 (Allowed in Approved mode)
|Digital Signature | | DSAforSSL | |Allowed for use within the TLS protocol
|Digital Signature | | RSAforSSL | |Allowed for use within the TLS protocol
|Message Digest | | MD5 | |FIPS 180-2
Random Number Generation | Universal Software Based Random Number Generator | Available upon request from IBM. Patented by IBM, EC Pat. No. EP1081591A2, U.S. pat. Pend.

Note:
The com.ibm.crypto.fips.provider.IBMJCEFIPS class does not include a keystore (such as JKS or JCEKS) because of FIPS requirements and algorithms. Therefore, if you are using com.ibm.crypto.fips.provider.IBMJCEFIPS and require JKS, you must specify the com.ibm.crypto.provider.IBMJCE in the provider list.

For more detailed information on the FIPS certified provider IBMJCEFIPS, see the IBM Java JCE FIPS 140-2 Cryptographic Module Security Policy. For usage information and details of the API, see the IBM Java JCE FIPS (IBMJCEFIPS) Cryptographic Module API document. These documents are available at http://www.ibm.com/developerworks/java/jdk/security/index.html.

## Differences between IBM and Sun versions of IBMJCEFIPS

Sun does not provide IBMJCEFIPS.

## What's new?

|No updates since v1.4.2.

## Documentation

For detailed information, including API documentation and Security Policy, see the developerWorks Web site, at http://www.ibm.com/developerworks/java/jdk/security/index.html.

| | |

# IBM SASL Provider

|

Simple Authentication and Security Layer, or SASL, is an Internet standard |(RFC 2222) that specifies a protocol for authentication and optional establishment |of a security layer between client and server applications. SASL defines how |authentication data is to be exchanged but does not itself specify the contents |of that data. It is a framework into which specific authentication mechanisms |that specify the contents and semantics of the authentication data can fit.

|

The Java SASL API defines classes and interfaces for applications that |use SASL mechanisms. It is defined to be mechanism-neutral: the application |that uses the API need not be hardwired into using any particular SASL mechanism. |The API supports both client and server applications. It allows applications |to select the mechanism to use based on desired security features, such as |whether they are susceptible to passive dictionary attacks or whether they |accept anonymous authentication. The Java SASL API also allows developers |to use their own, custom SASL mechanisms. SASL mechanisms are installed by |using the Java Cryptography Architecture (JCA).

|

The IBMSASL provider supports the following client and server mechanisms.

|

|
Client mechanisms
|
  |
  |
  - PLAIN (RFC 2595). This mechanism supports cleartext username/password |authentication.
  |
  - CRAM-MD5 (RFC 2195). This mechanism supports a hashed username/password |authentication scheme.
  |
  - DIGEST-MD5 (RFC 2831). This mechanism defines how HTTP Digest Authentication |can be used as a SASL mechanism.
  |
  - GSSAPI (RFC 2222). This mechanism uses the GSSAPI for obtaining authentication |information. It supports Kerberos v5 authentication.
  |
  - EXTERNAL (RFC 2222). This mechanism obtains authentication information |from an external channel (such as TLS or IPsec).
  |
|
Server mechanisms
|
  |
  |
  - CRAM-MD5
  |
  - DIGEST-MD5
  |
  - GSSAPI (Kerberos v5)
  |
|

| |

## Differences between Sun and IBM SASL Provider

|

Only the package names, for example "com.ibm.security.sasl", and the provider |name are different from the Sun Implementation: com.ibm.security.sasl.IBMSASL

| |

## What's new

|

The IBM SASL Provider is new for v5.0

| |

## Documentation

|

Detailed information, including API documentation and samples, is |on the developerWorks Web site, athttp://www.ibm.com/developerworks/java/jdk/security/index.html.

| | |

# Key Certificate Management utilities

|

The Key Certificate Management utilities make up a set of packages used |to:

|

|
- Access keys and certificates stored in any format
|
- Extract information from a KeyStore, given a Subject Key Identifier (SKI) |and a set of certificate generation APIs, to create a self-signed certificate
|
- Generate a CertificateRequest
|
- Obtain a certificate signed by a CA

|

The Key Certificate Management utilities can:

|

|
- Generate a CertificateRequest, and submit the request to a CA using the |Java PKI to sign a certificate and then receive the signed certificate
|
- Generate a PKCS10 request
|
- Generate a Self-Signed Certificate
|
- Revoke a signed certificate from a CA using the Java PKI
|
- Import certificates from the input stream to the KeyStore or export certificates |from the KeyStore to the output stream
|
- Copy a keystore from one keystore format to another keystore format.
|
- Extract information from a KeyStore given a Subject Key Identifier

|

The Subject Key Identifier is specified in RFC 3820, Section 4.2.1.2, http://www.faqs.org/rfcs/rfc3820.html.

| |

## What's new

|

The Key Certificate Management utilities are new for Version 5.0, Service |Refresh 1.

| |

## Documentation

|

The Key Certificate Management How-to Guide and |Javadoc are on the developerWorks Web site, at http://www.ibm.com/developerworks/java/jdk/security/index.html.

# Notices

This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:

- IBM Director of Licensing
  IBM Corporation
  North Castle Drive, Armonk
  NY 10504-1758 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

- IBM World Trade Asia Corporation Licensing
  2-31 Roppongi 3-chome, Minato-ku
  Tokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

- JIMMAIL@uk.ibm.com
  [Hursley Java Technology Center (JTC) contact]

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

## Trademarks

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Other company, product, or service names may be trademarks or service marks of others.

This product is also based in part on the work of the FreeType Project. For more information about Freetype, see http://www.freetype.org.

This product includes software developed by the Apache Software Foundation http://www.apache.org/.