Nils Larsch wrote: > which reader driver do you use ?
openct > correct, looks like a bug. It would be interessting to take a look at the > logs to see why the pkcs11 lib fails. Ok, I generated opensc logs with debug = 3 in different steps: 1) open thunderbird 2) decrypt a message 3) run pkcs11-tool -I 4) try to reopen the same message 5) close thunderbird The complete logs after every operation are available on http://www.alexdupre.com/pkcs11/[1-5].log so that it should be easy to make diffs between them. >> Second scenario: PKCS#11 lib with lock_login = false >> 1) start thunderbird >> 2) read an encrypted message (it asks user pin, but fails to decrypt the >> message, the PKCS#11 lib is unusable) > > could you try a recent snapshot if you still get this behaviour ? I don't see opensc commit related to locking after the 0.11.1 release. Did I miss something? In any case I generated logs for the following operation with lock_login set to true and false: echo hello | pkcs11-tool -s --pin 123456 The results are on: http://www.alexdupre.com/pkcs11/opensc-debug-lock.log http://www.alexdupre.com/pkcs11/opensc-debug-nolock.log http://www.alexdupre.com/pkcs11/opensc-errors-nolock.log If you confirm me that this bug may be already addressed in svn I'll try a snapshot. -- Alessandro _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
