JavaTM Secure Socket Extension 1.0.3

Known Bugs

  1. If JSSE receives a fatal SSL alert message, it invalidates the current session and closes the socket. It should also throw an exception stating the cause of the problem, but currently doesn't. Later operations such as read() or write() on the socket will correctly report that the socket is closed, but with no reason given.

  2. The "PKCS12" KeyStore type included in the JSSE reference implementation security provider only supports load() but not save(). This means that the keytool utility may be used to view but not edit pkcs12 files. The implementation supports PBEWithSHAAnd3KeyTripleDES for shrouded private keys and PBEWithSHAAnd40BitRC2 for safe contents elements. This should be compatible with PKCS12 files exported by Netscape Communicator version 4.04 and later. PKCS12 files using other algorithms can first be imported to Communicator and then exported in a compatible format.

    PKCS12 KeyStores can also be edited by the Java(TM) 2 Standard Edition v. 1.4.2_05 or later, or the Java(TM) 2 Platform Standard Edition 5.0 Development Kit (JDK 5.0) or later.

Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved.

Please send comments to: java-security@sun.com.