Release Notes

2 New Features
RSA BSAFE Crypto-C Micro Edition 4.1.4 Release Notes
New Features
This release of Crypto-C ME is designed to include the following new features:
Asymmetric key assurance and validation functions,
R_PKEY_validate_init_PKEY() and R_CR_validate_key(), which
allow parameters and keys to be checked for specific security requirements. A
number of validation methods are available:
SP 800-56A Rev 2 method for:
FIPS 186-4 generated keys and parameters
FIPS 186-2 generated keys and parameters
Generic method which checks numeric properties of keys and parameters.
For more information see the Asymmetric Key Management > Asymmetric
Key Assurance and Validation section in the RSA BSAFE Crypto-C Micro
Edition Developers Guide.
The FIPS 140-2 dynamic library files are no longer compatible with older
versions of Crypto-C ME. Applications must rebuild against this release of
Crypto-C ME. For more information see Binary Incompatibility with Previous
Versions of Crypto-C ME in the RSA BSAFE Crypto-C Micro Edition Migration
Guide.
The FIPS 140-2 provider defaults to the FIPS 140-2 mode of operation. For more
information, see FIPS 140-2 Mode is the Default Mode in the RSA BSAFE
Crypto-C Micro Edition Migration Guide.
Support for ARM
®
64 assembly optimizations, including hardware accelerated
AES, SHA-1 and SHA-256. These optimizations are automatically enabled on
supported hardware and can be disabled using
R_STATE_disable_cpu_features() with the ARMv8-specific options.
For more information see API Reference Information > Library State
Operations > Library State CPU Options > ARM64 (ARMv8 AArch64) CPU
Options section in the RSA BSAFE Crypto-C Micro Edition Developers Guide.
The Elliptic Curve (EC) asymmetric key format conforms to RFC 5915. For more
information see Elliptic Curve Asymmetric Key Format in the RSA BSAFE
Crypto-C Micro Edition Migration Guide.
Key wrap functionality to allow wrapping of symmetric or asymmetric key data
with either symmetric or asymmetric keys. Included are new:
Algorithm identifiers for key wrapping using a recipient's public key:
R_CR_ID_KW_KEM_KWS
R_CR_ID_KW_RSA_OAEP
R_CR_ID_KW_RSA_OAEP_SHA1
R_CR_ID_KW_RSA_OAEP_SHA256