RSA announces the release of RSA BSAFE® Crypto-J 6.2.5.
This release of Crypto-J is designed to provide the following new features:
- Updated Algorithm support:
- Implementations of SHA3-224, SHA3-256, SHA3-384, SHA3-512, SHAKE128, SHAKE256 available using the JCE MessageDigest API.
- Implementation of HKDF available using the JCE API.
- Implementation of HMAC/SHA3-224, HMAC/SHA3-256, HMAC/SHA3-384, HMAC/SHA3-512 and CMAC available using the JCE
- Implementation of ChaCha20, available using the JCE API.
- Implementation of Poly1305, available using the JCE API.
- Implementation of ChaCha20-Poly1305 AEAD cipher, available using the JCE API.
- Crypto-J gives deprecation warnings during compilation. In previous releases, deprecated Crypto-J classes and class members were only documented as being deprecated.
This release also addresses security issues. For details about security issues resolved please refer to the DSA-2019-094: RSA BSAFE® Crypto-J Multiple Security Vulnerabilities
For additional details of enhanced features and resolved issues with Crypto-J 6.2.5, please see RSA BSAFE® Crypto-J 6.2.5 Release Notes .
This release of Crypto-J is also compatible with SSL-J and Cert-J 6.2.4.x. Upcoming releases of SSL-J and Cert-J 6.2.4.x will include Crypto-J 6.2.5.
For additional documentation, downloads, and more, visit the RSA BSAFE page on RSA Link.
FIPS Validation Status:
The Crypto-J 6.2.5 module is in the FIPS 140 validation process. You can track the progress of the module on the Modules In Process List posted by the Cryptographic Module Validation Program (CMVP) at https://csrc.nist.gov/Projects/cryptographic-module-validation-program/Modules-In-Process/Modules-In-Process-List
RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details.