Reference Guide

68 Chapter 6: Changes Between Releases 4.1.2 and 4.1.4
RSA BSAFE Crypto-C Micro Edition 3.x to 4.1.4 Migration Guide
Elliptic Curve Private Key Format
Crypto-C ME 4.1 introduced new write formats for elliptic curve (EC) private keys for
the following functions:
• R_PKEY_to_binary()
•
R_PKEY_to_bio()
•
R_PKEY_to_file()
R_PKEY_to_binary() now writes in the format described in RFC 5915. To write
EC private keys in the pre-4.1 legacy format, set the format by calling
R_PKEY_set_info() with R_PKEY_INFO_ID_DEFAULT_ENCODING and
R_PKEY_FORMAT_PKCS8 before calling R_PKEY_to_binary().
R_PKEY_to_bio() and R_PKEY_to_file() now write EC private keys, to a BIO or
file, in a specified format. Choosing the
R_PKEY_FORMAT_BINARY format writes in the
format described in RFC 5915, while choosing the
R_PKEY_FORMAT_PKCS8 format
writes objects in the legacy format.
For more information about these functions and identifiers, see API Reference
Information in the RSA BSAFE Crypto-C Micro Edition Developers Guide.
Binary Incompatibility with Previous Versions of
Crypto-C ME
The FIPS 140-2 resource dynamic library files in Crypto-C ME 4.1.4 are not
compatible with older versions of Crypto-C ME. Applications must be rebuilt with
Crypto-C ME 4.1.4 to use the Crypto-C ME 4.1.4 FIPS cryptographic module.
Signature Files Embedded into the FIPS 140-2 Master
Library File
The signature files for FIPS 140-2 tests (cryptocme.sig2 in Crypto-C ME 3.x, and
cryptocme.sig and cryptocme_test_on_use.sig in earlier Crypto-C ME 4.x
releases) are now embedded into the FIPS 140-2 master library file for Crypto-C ME
4.1.4.