Hello!

First I want to thank you for your work on this library.

But sadly, we came upon an issue with the pkcs#11 interface of opensc with the Aladin eToken 32k, using opensc-0.11.9 (linux/macosx).

In our use case we have two pin storages on one token, created with the pkcs15-init tool. Now we want to store keys and data to the different pin locations of the token. Unfortunately even storing only CKO_DATA objects on different PIN protected parts don't work.

I get errors like:

[opensc-pkcs11] pkcs15-lib.c:3431:sc_pkcs15init_update_file: File 3f0050153404 too small (require 93, have 41) - please increase size in profile
Error in C_CreateObject error code: 5
[opensc-pkcs11] card-cardos.c:259:cardos_check_sw: required access right not granted [opensc-pkcs11] iso7816.c:290:iso7816_update_binary: Card returned error: Security status not satisfied [opensc-pkcs11] card.c:514:sc_update_binary: returning with: Security status not satisfied
Error in C_CreateObject error code: 257
.

Attached to this email there is a small program that can reproduce this error. The error above will appear on the second run.

The funny thing is, that if I write data to one PIN protected area, then release all resources and reload the pkcs#11 library, accessing the second protected pin area works quite right. But if I don't unload the library it seems that the underlaying pkcs15 structures on the token is compromised, so that the reloading strategy does not work anymore.


Greetings,

Roman Himmes


Attachment: token_test.cpp.bz2
Description: BZip2 compressed data

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to