Reference Guide

6 Chapter 1: Library and Header File Changes
RSA BSAFE Crypto-C Micro Edition 3.x to 4.1.4 Migration Guide
New Library Files
Crypto-C ME 4.0 introduced a provider model, resulting in changed library files an
application must link to.
There are now four static library files an application can link to depending on the
functionality required (the names differ depending on the platform):
•
ccme_core. The main library containing the generic functions and
implementations for the library that were previously found in both the standard
and FIPS140 libraries. This library file is always required.
•
ccme_swprov. Contains the software implementation previously found in the
cryptocme_standard library file. If using the software provider,
mes_swprov should be included on the link line before ccme_core.
•
ccme_fipsprov. Contains the FIPS 140-2 provider implementation previously
found in the
cryptocme_fips140 library file. If using the FIPS140-2 provider,
ccme_fipsprov should be included on the link line before ccme_core.
•
ccme_p11prov. Contains the PKCS #11 provider implementation previously
found in both the
cryptocme_standard and cryptocme_fips140 library
files. If PKCS #11 functionality is required,
ccme_p11prov should be included
on the link line before
ccme_core.
The
ccme_core library files provides the standard Crypto-C ME functionality and
must always be linked with the application. Any combination of the other libraries can
be linked into the application as required.
The following table lists the library files used for Crypto-C ME 3.x and
Crypto-C ME 4.1.4
Table 1 Library Files
Library File Type Crypto-C ME 3.x Crypto-C ME 4.1.4
Static
cryptocme_standard
cryptocme_fips140
ccme_core
ccme_swprov
ccme_fipsprov
ccme_p11prov
Master Dynamic
cryptocme2
cryptocme
FIPS 140-2 Resource
Dynamic
ccme_base
ccme_ecc
ccme_eccaccel
ccme_eccnistaccel
ccme_base
ccme_base_non_fips
ccme_asym
ccme_aux_entropy
ccme_ecc
ccme_ecc_non_fips
ccme_ecc_accel_fips
ccme_ecc_accel_non_fips
ccme_error_info