On Mon, Jul 23, 2012 at 9:00 AM, NdK <ndk.cla...@gmail.com> wrote: > The problem with FF (and TB) is that it calls C_login only once, then > assumes the login is still valid. Even if card got reset.
Then you should return the appropiate PKCS#11 error values, and thats all. Isnt it so? > Even worse, it asks for *ALL* PINs when the token gets added. > That made me give up having pkcs#11 enabled in FF/TB. I have mine added with not so many problems, so if you want some help, contact me. In fact, this week a added a third device without problems... > IIRC there are a couple of bug reports in bugzilla, but seems they won't get > fixed. Really? XD > "Friendly token" (or something similar...) setting helps a bit, but IMO > it remains unsafe to have a token accessed by FF. "-mechanisms FRIENDLY"? IIRC, it enable accessing the token without requiring a PIN at first load, then it ask for it when trying to use certificates. Always at your service Diego! PS: [OT] A few days ago i used Java PKCS#11 interface using C_whatever functions in java (we are actually using SunPkcs11 provider), and seems to be working ok. IMHO its "easier" than smartcard-io. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
