Hi Peter,
sorry for the delay, I have been out of office.
When I delete the lines 1309-1314, nothing is better with
the TCOS card via Xiring. And the PIN of the CardOS card is not
accepted by firefox despite the fact, that you still can verify it
via opensc-tool.
Below I insert the analysis of
2011/7/19 Peter Koch :
> Hi Martin!
>
> 2011/7/18 Martin Paljak
>>
>> > Some reader expect just 4 bytes (CLA INS P1 P2) without Le. Some other
>> > readers insist on getting a 0-Le byte. And very few readers handle both
>> > cases.
>>
>> This should be tested and documented if possible. Creating c
Hi Martin!
2011/7/18 Martin Paljak
> > Some reader expect just 4 bytes (CLA INS P1 P2) without Le. Some other
> > readers insist on getting a 0-Le byte. And very few readers handle both
> cases.
>
> This should be tested and documented if possible. Creating conditional
> reader-specific code is
Hello,
On Jul 17, 2011, at 00:34 , Peter Koch wrote:
> Control TxBuffer: 1E 1E 02 00 00 10 06 02 FF 00 00 00 00 00 00 05 00 00 00 00
> 20 00 00 00
> -> 00 69 14 00 00 00 00 39 00 00 00 00 1E 02 00 00 10 06 02 FF 00 00 00
> 00 00 00 00 20 00 00 00
> <- 00 80 02 00 00 00 00 39 00 00 00 6B
Hi Johannes!
2011/7/15 Johannes Becker
> Hello,
>
> I'm testing a new Firmware for the Xiring MyLeo card reader. It
> will support extended APDU. It works with a CardOS chip, but
> with a TCOS chip firefox displays quickly the small window asking
> you to enter the pin on the pinpad several time
Hello,
I'm testing a new Firmware for the Xiring MyLeo card reader. It
will support extended APDU. It works with a CardOS chip, but
with a TCOS chip firefox displays quickly the small window asking
you to enter the pin on the pinpad several times. You have no chance
to do so and there is subsequ
