|Applies To||RSA BSAFE Micro Edition Suite|
|Issue||MES: How to enable RC5 if an RC5 operation fails with error R_ERROR_NOT_FOUND (10008)|
An RC5 operation fails with error R_ERROR_NOT_FOUND (10008) (e.g. R_CM_decrypt returns R_ERROR_NOT_FOUND (10008) when reading a PKCS #7 envelope where content encryption key is RC5)
RC5 works in MES 3.0.x but not MES 3.1
|Resolution||MES supports RC5, but it is not included in the default resource list.|
RC5 works in MES 3.0.0.x non-FIPS with the default resource list, because the library accidentally pulls in another resource list and NO_RC5 define does not work as intended.
In MES 3.1, is not in the default resource list. To use RC5, use a custom resource list that includes RC5.
This behavior of MES3.1 is correct. What MES3.0.0.x is doing is wrong.
|Legacy Article ID||a43044|