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

[Huie-Ying Lee]

Massimiliano Pala wrote:
> Wyllys Ingersoll wrote:
> [...]
>> Well, considering I *never* code in C++ might explain the
>> difference in styles :)
> 
> Well, me neither... but I like the concept of providing wrapping
> functions so that apps do not mess with libraries :)
> 

I would like to make sure that I understand correctly about your wrapping
function suggestion.

Is a wrapping function basically a get or a set function which
retrieve or set the value of a field for a complicate and opaque data structure ?

If the answer is yes, then for CSR operation, KMF already provides
some SET* functions:

      KMF_SetCSRPubKey(KMF_HANDLE_T, KMF_KEY_HANDLE *, KMF_CSR_DATA *);
      KMF_SetCSRVersion(KMF_CSR_DATA *, uint32_t);
      KMF_SetCSRSubjectName(KMF_CSR_DATA *, KMF_X509_NAME *);
      KMF_SetCSRExtension(KMF_CSR_DATA *, KMF_X509_EXTENSION *);
      KMF_SetCSRSignatureAlgorithm(KMF_CSR_DATA *, KMF_ALGORITHM_INDEX);
      KMF_SetCSRSubjectAltName(KMF_CSR_DATA *, char *, int, KMF_GENERALNAMECHOICES);
      KMF_SetCSRKeyUsage(KMF_CSR_DATA *, int, uint16_t);

Although there is no Get function for CSR at this moment, they can be added easily.

Is this what you are looking for ?


-- Huie-Ying