Hi,
On Thu, Dec 27, 2012 at 04:26:38PM +0100, Ludovic Rousseau wrote:
> I do not like it at all but we may have lose all the bugs reported at
> opensc-project.org and start a new collection at github.
There's some valuable stuff in Trac like a GemSafeV2 driver which
never got merged (http://www.o
Hi,
I've issued pull request #111 which enhances pkcs15-gemsafeV1.c
by two features:
(1) Multiple key containers are now supported.
Previously the code would only make the first certificate found
on the card available to the user. By reverse-engineering the
USB communication of the
Hi,
On Mon, Dec 03, 2012 at 11:20:14AM +0100, Viktor Tarasov wrote:
> In OpenSC the '0C' value for P2 is used when there is no need to return FCI
> data in 'SELECT' command:
Aha. Thanks. I was wondering where the additional key containers are stored
on the card and thought that maybe P2 = 0C woul
Hi,
I've got a GemSafeV1 card here which has 10 key containers. The native
Gemalto Windows driver shows that there's a certificate in the third
and fourth key container, all others are empty.
OpenSC only sees the certificate in the third key container.
Using a USB Sniffer I can see that the nati
On Thu, Nov 22, 2012 at 01:44:45PM +0200, Martin Paljak wrote:
> On Sun, Oct 14, 2012 at 3:27 PM, Ludovic Rousseau
> wrote:
> > I would suggest to drop the OpenSC tokend, unless someone volunteer to
> > maintain it.
> I think my current mbp running 10.7 will be the last piece of Applet
> hardware
Hi,
when logging in to a GemSafeV1 card with 0.13.0rc1, opensc first retrieves
the number of tries_left using C_GetTokenInfo() and then calls C_Login().
Both functions invoke sc_pin_cmd() to communicate with the card.
It seems that somehow in-between the two invocations of sc_pin_cmd(),
the sc_pk
