CKA_GLOBAL and uniqueness

[Stef Walter <stefw@redhat.com>]

Hi Mike,

Apologies for not writing this earlier...

In general I like the concept of being able to tag objects with the
CKA_GLOBAL attribute.

However the part about making sure the objects are unique and
identifiable (via CKA_OBJECT_ID and CKA_CLASS) are less obvious,
especially for this point version of the PKCS#11 spec.

Have you thought about it in the context of a more general object
uniqueness solution? I think that we'll want to have discussions about a
unique/static handle/identifier in the 3.0 spec, and my concern is that
there would be two different solutions.

In addition, it seems that we add CKA_OBJECT_ID as an attribute that
nearly every class can have. Does that mean it's always present (and
empty) for all the common storage classes?

On the other hand, if we do come up with a different uniqueness solution
for 3.0, we could remove the solution applied to CKA_GLOBAL.

So can your proposal survive without the last 5 paragraphs? Is the
solution dependent on this part?

Cheers,

Stef