If you have not used the cryptoadm command to enable FIPS-140 support in snv_124 or afterward, you can safely discard this heads-up.
The FIPS-140 mode setting was originally kept in /etc/crypto/kcf.conf. With my recent integration to snv_128 for CR 6897371, this setting is now saved in a different configuration file. If you've enabled FIPS-140 support before snv_128 and then bfu'ed to snv_128 (or later), the cryptosvc service will not start because of the old FIPS status in kcf.conf. To fix this, edit /etc/crypto/kcf.conf, removing the line starting with "fips-140:", and reboot. The bfu script will be updated soon to handle this automatically. Sorry for the inconvenience. Hai-May
