Please review proposal "Interfaces and Function Lists v2"

All,

 

as per yesterday’s minutes, this is the friendly reminder to review my proposal "Interfaces and Function Lists v2".

The public download link is 
https://www.oasis-open.org/committees/download.php/63797/interfaces_and_functions_list_v2.docx

 

There are 2 main discussion points:

 

1. I’ve provided a proposal for C_GetInterfaceList and 3 variants of it. The proposal is similar to C_GetFunctionList, i.e. a pointer to the list of interfaces inside the library is returned. This is the most simple approach.
 In Variant 1, the application has to allocate a buffer for the char pointer array, but the actual interfaces names are still in the library. This was my original proposal but I think it does not really make sense. Variant 2 follows the style of C_GetAttributeValue
 when returning a template attribute. Big drawback is that you actually have to call it three times! I won’t recommend it but added it for completeness. In Variant 3 the interface name length is fixed. Actually, this is common in PKCS#11 and it might be preferred
 anyway. Thus, we could use variant 3 where the application allocates a buffer and library copies everything to that buffer, or we could use the proposal from the main part of the document, but set a fixed name length anyway.

 

2. Must “PKCS 11 2.40” and “PKCS 11 3.0” always be returned by C_GetInterfaceList or can C_GetInterfaceList also return only additional interfaces, which could be none?

 

Thanks,

Daniel

 

Utimaco IS GmbH

Germanusstr. 4, D.52080 Aachen, Germany, Tel: +49-241-1696-0, www.utimaco.com

Seat: Aachen – Registergericht Aachen HRB 18922

VAT ID No.: DE 815 496 496

Managementboard: Malte Pollmann (Chairman) CEO, Dr. Frank J. Nellissen CFO

This communication is confidential. We only send and receive email on the basis of the terms set out at https://www.utimaco.com/en/e-mail-disclaimer/