pkcs11 — archive

[Michael StJohns]

On 4/8/2013 3:13 PM, Robert Relyea wrote: On 04/03/2013 03:25 PM, Burns, Robert wrote: Exact structure from our v2.10 'virgin' pkcs11t.h file shows the error as well, along with conflicting naming using the ‘ul’ construct: /* CK_PKCS5_PBKD2_PARAMS is new for v2.10. * CK_PKCS5_PBKD2_PARAMS is a structure that provides the * parameters to the CKM_PKCS5_PBKD2 mechanism. */ typedef struct CK_PKCS5_PBKD2_PARAMS { CK_PKCS5_PBKDF2_SALT_SOURCE_TYPE           saltSource; CK_VOID_PTR pSaltSourceData; CK_ULONG ulSaltSourceDataLen; CK_ULONG                                   iterations; CK_PKCS5_PBKD2_PSEUDO_RANDOM_FUNCTION_TYPE prf; CK_VOID_PTR                                pPrfData; CK_ULONG                                   ulPrfDataLen; CK_UTF8CHAR_PTR                            pPassword;         CK_ULONG_PTR            ulPasswordLen; } CK_PKCS5_PBKD2_PARAMS; Does the question now become one of backwards compatibility if we have some vendors who fixed the flaw, and others who implemented it as documented and declared in the previously published headers? Bob I've checked our implementation, and we treat it as a CK_ULONG_PTR, just as the spec and header file specify, even though it's clearly a typo. bob I'd leave it as is.  It's consistent in the text and in the header files.   If it needs to be changed, then the proper way is to define a new structure and mechanism and leave this one intact. Mike