My java application handle multi access to the smart card - no problem, but I think that already the PKCS11 library should do this. It should be on this level, because it need not be threads, but applicatons. E.g. many application (or threads) should be logged on, and when one of them sign data, the another application will wait (for example when user is logging on, or signing data too) -> it really means that PKCS11 library will wait to process the call of the function from application.
On the other hand, it maybe won't be so simple as I wrote in my first message... I think of that, because it possible with SafeSign PKCS11 library (libaetpkss.so), which is shipped with iKey 3000 USB token (it is not open source, I decided it from the behaviour). Should you describe me, what is lock_login parameter really for? Regards, Petr Bunka -----Original Message----- From: Andreas Jellinghaus [mailto:[EMAIL PROTECTED] Sent: Thursday, October 19, 2006 8:22 AM To: Bunka, Petr Cc: opensc-devel@lists.opensc-project.org Subject: Re: [opensc-devel] OpenSC PKCS#11 module lock I'm not 100% sure, but the way smart cards work you can not access them by more than one application at the same time. So what the library can do is between major operations alternate who can use it, but true double use can never be archived. It might be easiest to not even try. Think of: if you want to sign some data, but the user has to enter the pin on the smart card readers pinpad, then nothing can happen until the user does so or the operation times out. multi threading or not, lock_login or not, your application should better be designed so it can handle this situation. but again I'm no expert on this, even less on java. it is only the basic design problem found using smart cards. Regards, Andreas This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
