2011/5/9 Jean-Michel Pouré - GOOZE :
> Dear Alon,
>
> Could you comment the alternative, where OpenSC would behave as a
> client-server application pooling access requests from applications and
> locking the card in exclusive mode, i.e. work as a proxy.
>
> Kind regards,
Hi,
This had been raised l
This is a matter of interpretation.
Either is not constant and user is not suppose to know of.
Apart of the special case of having a single slot, so you expect 0 I presume.
You can check which slot is what simply by using:
pkcs11-tool --list-slots --module /usr/lib/pkcs11/
On Mon, May 9, 2011
Hello,
A small status update on OpenSC 0.12.1 release, which was planned to be rolled
out yesterday.
Something has happened to the virtual machines that run the builders, they need
to be re-started.
But unfortunately I'm on a sudden trip to Beijing for the past few days (and
will be a few day
Hello,
A small status update on OpenSC 0.12.1 release, which was planned to be rolled
out yesterday.
Something has happened to the virtual machines that run the builders, they need
to be re-started.
But unfortunately I'm on a sudden trip to Beijing for the past few days (and
will be a few day
Hello,
I think I've found a bug in the OpenSSL engine_pkcs11.
The slot_index supplied from the command line to OpenSSL and actually
directed to engine_pkcs11, is incorrectly parsed by the latter which
treats it as if it were the slot_id.
Most pkcs#11 implementations assume slot_index = slot_i
Le samedi 07 mai 2011 à 23:43 +0300, Alon Bar-Lev a écrit :
> The authentication cookie solves above, PINPAD, BIO efficiently,
> however it requires card to support it. You get a cookie out of
> PIN/PINPAD operation/BIO match. The cookie is valid as long as card is
> powered on and policy permits.
