G'day,

Chris Osgood wrote:
A while ago I had made a patch dealing with data objects where the
CKA_VALUE was being stored in the attribute file under certain
circumstances (which usually causes the attribute file to run out of
space).  I do not know if this will fix your problem but it might be
worth a try.  See attached patch for p11_object.c

I applied the patch, but I still can view only one data object, regardless of how many data objects I create.

I also used muscleTool to verify this.

On an empty card, there are no objects present:

muscle [MuscleCard Applet] > list
           Object ID  Object Size     READ   WRITE   DELETE
   -----------------  -----------    ------  ------  ------
ERR: ListObjects Failed (0x9C12 End of sequence)

After I create one data object on the card, muscleTool shows the following:

muscle [MuscleCard Applet] > list
           Object ID  Object Size     READ   WRITE   DELETE
   -----------------  -----------    ------  ------  ------
                  o0          512    ALWAYS  PIN #1  PIN #1
                  O0            3    PIN #1  PIN #1  PIN #1

The object with ID "O0" represents the 3-byte value of the PKCS#11 data object, the object with ID "o0" presumably represents the other PKCS#11 attributes.

I can view the data object using PKCS#11 commands, but when I delete file with object ID "o0", then I cannot view the data object using PKCS#11 commands.

Next, if I create three PKCS#11 data objects, then use muscleTool to list the contents of the card, I get the following:

muscle [MuscleCard Applet] > list
           Object ID  Object Size     READ   WRITE   DELETE
   -----------------  -----------    ------  ------  ------
                  O0            3    PIN #1  PIN #1  PIN #1
                  o0          512    ALWAYS  PIN #1  PIN #1


This is the same object list as creating one PKCS#11 data object. Using PKCS#11 if I create three objects and find objects in the same session, then the find returns the three newly-created objects. If I pause between creating the data objects and viewing them in the one session, then muscleTool still shows the two objects listed above. So I assume that some form of caching is occuring in libmusclepkcs11 here?

-- Geoff

_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to