Reference Guide

30 Chapter 3: Resource Management
RSA BSAFE Crypto-C Micro Edition 3.x to 4.1.4 Migration Guide
Custom Resource Lists
Unlike Crypto-C ME 3.x where cryptographic algorithms were a different type of
resource found in a sub-list, with Crypto-C ME 4.1.4 all resources are treated the
same. One custom list can be used to hold all required resources, or multiple custom
lists can be added to the library context separately if you want to categorize resources.
The following table lists the resources changed between Crypto-C ME 3.x and
Crypto-C ME 4.1.4.
Crypto-C ME 4.1.4 also introduces new fine-grained resources that remove the need
to customize method tables to drop functionality and code from the final application.
Where previously with Crypto-C ME 3.x, applications implemented a custom method
table for the
R_CR API, with Crypto-C ME 4.1.4 there are resources that implement
the generic algorithm class that can be explicitly specified in the resource list. This is
the same for other components in the system such as the asymmetric key
implementation, which has resources for each key type, and the data conversion
implementations, such as to and from binary, PEM, and PKCS #8.
Table 7 Resources Changed
Crypto-C ME 3.x Crypto-C ME 4.1.4
R_LIB_RES_DEFAULT
No longer available.
R_LIB_RES_DUP
No longer available.
R_CR_RES_SOFTWARE_METHS
Replaced by the software provider, or by using the
software provider resources directly.
R_CR_RES_HARDWARE_METHS
Replaced by the PKCS #11 provider.
R_CR_RES_CRYPTO_ARBITRATOR
No longer available. More advanced functionality
built into the library context.
R_DMEM_RES_DEFAULT
No longer required. Still available but does
nothing.
R_HW_RES_CONFIG_DEFAULT_DATA
Replaced by PKCS #11 feature
R_PROV_PKCS11_feature_config_from_env
R_HW_RES_DEFAULT
No longer available.
R_HW_RES_LOGIN
Replaced by PKCS #11 feature
R_PROV_PKCS11_feature_auth
R_HW_RES_LOGIN_CB
No longer available.
R_HW_RES_SEARCH
No longer available.