|
Description
|
The initial kcf.conf file is empty (has no entries). Disable a mechanism
on a kernel software provider via cyrptoadm will write an entry to
kcf.conf. Followed by one or more attempts to disable a mechanism on
different kernel software provider.
Subsequent enabling or disabling mechanisms on the kernel software providers
in kcf.conf except for the last provider's entry will cause the identical
entries to be created in kcf.conf file.
For example:
# cryptoadm disable provider=des mechanism=CKM_DES_ECB
# cryptoadm disable provider=aes mechanism=CKM_AES_CTR
# cryptoadm enable provider=des mechanism=CKM_DES_ECB
# cryptoadm disable provider=aes mechanism=CKM_AES_GCM
The entries in kcf.conf now become:
des:supportedlist=CKM_DES_ECB,CKM_DES_CBC,CKM_DES3_ECB,CKM_DES3_CBC
aes:supportedlist=CKM_AES_ECB,CKM_AES_CBC,CKM_AES_CTR,CKM_AES_CCM,CKM_AES_GCM;disabledlist=CKM_AES_GCM,CKM_AES_CTR
des:supportedlist=CKM_DES_ECB,CKM_DES_CBC,CKM_DES3_ECB,CKM_DES3_CBC
aes:supportedlist=CKM_AES_ECB,CKM_AES_CBC,CKM_AES_CTR,CKM_AES_CCM,CKM_AES_GCM;disabledlist=CKM_AES_GCM,CKM_AES_CTR
|
