|
Description
|
When an application needs to generate a key to use for encryption with some pkcs11 mechanism, it also needs a way to find the key generation mechanism associated with that encryption mechanism. While it is possible to hard code the key gen mechanism, for example, if using CKM_AES_CBC the key gen mech is CKM_AES_KEY_GEN, that approach isn't very flexible. If the number of mechanisms supported grows, it also creates a maintenance issue. As the number of crypto-enabled applications also grows, the maintenance problem is compounded. Implementing the mapping centrally solves the problem once for any app that may need to use it.
|