Reference Guide

Chapter 1: Library and Header File Changes 7
RSA BSAFE Crypto-C Micro Edition 3.x to 4.1.4 Migration Guide
Migrate FIPS 140-2 Applications
Applications using FIPS 140-2-compliant cryptographic functionality, which
previously linked against the
cryptocme_fips140 library file, now link against the
ccme_core, and ccme_fipsprov library files. For PKCS #11 cryptographic
functionality, which was previously available in the
cryptocme_fips140 library
file, applications must also link against the
ccme_p11prov library file.
If disk or volume space is an issue, some resource shared library files can be removed.
For more information about these files and the circumstances under which they can be
removed, see Get Started with Crypto-C ME > FIPS 140-2-compliant
Applications > Remove Resource Shared Library Files in the RSA BSAFE
Crypto-C Micro Edition Developers Guide.
Migrate Non-FIPS 140-2 Applications
Applications using standard or software cryptographic functionality, which previously
linked against the
cryptocme_standard library file, now link against the
ccme_core, and mes_swprov library files. For PKCS #11 cryptographic
functionality, which was previously available in the
cryptocme_fips140 library
file, applications must also link against the
ccme_p11prov library file.
Migrate PKCS #11 Applications
Applications requiring only PKCS #11 cryptographic functionality, which previously
linked against either the
cryptocme_standard, or cryptocme_fips140 library
files, now need to link against the
ccme_core, and ccme_p11prov library files.