Reference Guide

56 Chapter 6: Changes Between Releases 4.1.2 and 4.1.4
RSA BSAFE Crypto-C Micro Edition 3.x to 4.1.4 Migration Guide
Note: Although the Crypto-C ME security strength checks can be disabled by setting
the minimum strength settings to zero, the protection strength check should never be
disabled in a production environment as it allows the library to use weak asymmetric
keys that provide no protection whatsoever.
Rather than disabling the check, the weak key should be removed from the
deployment and replaced by a strong key. There may be exceptional circumstances
where the processing strength check may be required to be disabled, where
pre-existing data has been previously protected by a weak key. This should only be
done in a production environment as a last resort. Preferably the data is transitioned to
strong protection in a non-production environment.