Release Notes

Known Issues 29
RSA BSAFE Crypto-J 6.2.5 Release Notes
Known Issues
The following table lists the known issues in this release of Crypto-J.
Table 22 Known Issues
ID Description
BSFCRYJ-1245 The default PBE iteration count is too low.
BSFCRYJ-1234 JsafeJCE interoperability issue with Oracle JSSE in JDK 7 on Solaris 11
when using DHE cipher suites.
BSFCRYJ-1161
jce.cms.WorkflowRSAOAEP and jce.cms.WorkflowRSAKEMKWS
samples fail in FIPS 140 mode (use 1024-bit RSA key).
BSFCRYJ-1139 Crypto-J no longer supports RSA Multi-prime. RSA Multi-prime is now
deprecated and will be removed in a future release.
BSFCRYJ-1072 In Android SDK: The
getInstance method in the Cipher
implementation does not return the JsafeJCE provider when JsafeJCE is
registered and the method is called without the Provider parameter. For
more details, go to
https://code.google.com/p/android-developer-preview/iss
ues/detail?id=3025
In Crypto-J: Cipher.getInstance without the Provider fails to return
JsafeJCE on Android 5.x higher.
This issue has been fixed on Android 7.
BSFCRYJ-1071 In Android SDK: The
getInstance method in the Cipher
implementation does not propagate NoSuchPaddingException even when
the JsafeJCE provider throws it. For more details, go to
https://code.google.com/p/android-developer-preview/iss
ues/detail?id=3026
In Crypto-J: Cipher.getInstance does not throw
NoSuchPaddingException on Android 5.x higher.
BSFCRYJ-1035 IBM JDK: FIPS186Random algorithm not allowable in FIPS140 mode.