Release Notes

34 Known Issues
RSA BSAFE Crypto-C Micro Edition 4.1.4 Release Notes
BSFCRYCME-1041 The R_RES_LIB_ERROR_STRINGS resource has a string table that
maps R_ERROR codes to string equivalents, but the table is missing
some values and contains
R_ERROR_BAD_PARAMETER, which is an
offset value.
BSFCRYCME-1036
R_PKEY_get_PEM_header() hides errors for PKCS #8 encoded
keys.
BSFCRYCME-1033 The
R_LOCK API cannot return memory allocation errors.
BSFCRYCME-1027 No application access to the cipher parameters in PBES2 for
generating PKCS #8 messages.
BSFCRYCME-998 Cannot return PBES2 encryption algorithm id from
R_PKEY
PKCS #8 data.
BSFCRYCME-887
The PKCS #11 provider does not track the session against keys stored
as session objects.
Workaround
If session keys are required in an application, there are two options:
• Use the deprecated
R_PROV_PKCS11_feature_auto_write_keys feature for
automatically storing keys before operations. Do not store keys
explicitly with
R_PKEY_store() or R_SKEY_store().
• Use the
R_PROV_PKCS11_feature_session_pool feature
and manually store keys immediately before initializing the
cryptographic operation with the key. Note that this approach
relies on the LIFO behavior of the session pool and is not reliable
for multi-threaded use.
BSFCRYCME-831
PKCS #11 provider API R_PROV_PKCS11_update_only() does
not clear stale sessions or log-in state.
BSFCRYCME-709 R_PKEY_to_bio() cannot enforce PKCS #1 formatting for keys
read from PKCS #8 data.
BSFCRYCME-115 Named curve C2ONB239V5 does not work with DSA.
Table 9 Known Issues (continued)
ID Description