Every function in the Cryptoki API MUST have an entry point defined in the Cryptoki library’s CK_FUNCTION_LIST structure. If a particular function in the Cryptoki API is not supported by a library, then the function pointer for that function in the library’s CK_FUNCTION_LIST structure should point to a function stub which simply returns CKR_FUNCTION_NOT_SUPPORTED.
Somewhat late on this one, but given how many implementations treat compliance with the spec merely as a "nice to have", it's probably safer to keep the check..
is_fn_supported()
returnstrue
for all libraries and functions I tested with. This makes sense when reading the spec:Both say: