OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

pkcs11 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Missing specification details for profile objects?



when comparing the “Profile objects” section of WD02 with some other sections I was wondering if it is missing some details.


First, other objects like the mechanism objects or the hardware feature objects contain this paragraph:

“When searching for objects using C_FindObjectsInit and C_FindObjects, mechanism objects are not returned unless the CKA_CLASS attribute in the template has the value CKO_MECHANISM. This protects applications written to previous versions of Cryptoki from finding objects that they do not understand."

IMO a similar paragraph should exist for profile objects.


Second, the mechanism objects explicitly states:

“The CKA_MECHANISM_TYPE attribute may not be set.”

IMO this should be true for the CKA_PROFILE_ID as well since a profile cannot be changed.


In fact, this statement seems to be too weak since a profile object cannot be created, copied or deleted. This is true for every non-storage object (i.e. hardware feature object, mechanism object, profile object). Do we need to clarify this?


Kind regards,



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: Stefan Auerbach (Chairman) CEO, Malte Pollmann CSO, Martin Stamm CFO

This communication is confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Please inform us immediately and destroy the email.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]