[kmf-discuss] Opinions wanted - new init/create APIs

[Wyllys Ingersoll]

Based on conversations with Max earlier, I think we
need some new APIs for initializing and allocating some
of our structures.

There are 2 ways that apps use the KMF structures, allocated
on the stack or allocated dynamically.  For each complex
structure, we may want 2 routines.

Example:
KMF_DATA *Alloc_KMF_DATA(void);  /* Allocate and initialize */
void Init_KMF_DATA(KMF_DATA *);  /* Initialize only */

Does this sound reasonable?   I would propose adding
such functions for the following structures:

KMF_X509_DER_CERT
KMF_CONFIG_PARAMS
KMF_CREDENTIAL
KMF_FINDCERT_PARAMS
KMF_DELETECERT_PARAMS
KMF_IMPORTCERT_PARAMS
KMF_VALIDATECERT_PARAMS
KMF_FINDKEY_PARAMS
KMF_STORECERT_PARAMS
KMF_STOREKEY_PARAMS
KMF_DELETEKEY_PARAMS
KMF_IMPORTCERT_PARAMS
KMF_CREATEKEYPAIR_PARAMS
KMF_IMPORTCRL_PARAMS
KMF_DELETECRL_PARAMS
KMF_LISTCRL_PARAMS
KMF_FINDCRL_PARAMS
KMF_FINDCERTINCRL_PARAMS
KMF_VERIFYCRL_PARAMS
KMF_CHECKCRLDATE_PARAMS
KMF_CRYPTOWITHCERT_PARAMS
KMF_SETPIN_PARAMS
KMF_RAW_KEY_DATA
KMF_EXPORTP12_PARAMS
KMF_CREATESYMKEY_PARAMS
KMF_OCSPREQUEST_PARAMS_INPUT
KMF_OCSPRESPONSE_PARAMS_OUTPUT
KMF_X509EXT_BASICCONSTRAINTS
KMF_X509EXT_CERT_POLICIES
KMF_X509EXT_AUTHINFOACCESS
KMF_X509EXT_CRLDISTPOINTS
KMF_X509EXT_KEY_USAGE
KMF_X509_ALGORITHM_IDENTIFIER
KMF_X509EXT_EKU
KMF_X509_TBS_CERT
KMF_X509_NAME
KMF_X509_EXTENSION
KMF_X509_CERTIFICATE
KMF_CSR_DATA
KMF_TBS_CSR
KMF_KEY_HANDLE

Thoughts ?

-Wyllys