Error with the korrigo card and calypso.lua script about cardpeek

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I can't reproduce the issue. I tested the Calypso script on a Korrigo card and 
it seems to work.

Perhaps you have changed your card reader or the driver of your card reader? 

In my case, I know I have trouble reading Korrigo cards with my Omnikey reader: 
I get the following message in the log tab:

0020 ERROR   Connection failed: Card is unpowered. (error 0x80100067).
0021 ERROR   Failed to query card status: Invalid handle. (error 0x80100003).

But my Gemplus reader works just fine... 

If you are using Linux, could you print the output of "pcsc_scan" with the 
corrigo card in the reader? 
If you are using Mac OS X, you can do the same with "pcsctest". 

Original comment by [email protected] on 24 Nov 2013 at 4:55

[GoogleCodeExporter]

It seems that there is a problem with my driver. I use the Omnikey reader too. 
When inserting the card pcsc_scan says:

Fri Nov 29 09:50:57 2013
Reader 0: OMNIKEY CardMan 5x21 (OKCM0072509121946310601228960981) 00 00
  Card state: Card inserted, Unresponsive card, 

what is surprising is that the reader successfully read the korrigo card in NFC 
!

Reader 1: OMNIKEY CardMan 5x21 (OKCM0072509121946310601228960981) 00 01
  Card state: Card inserted, 
  ATR: 3B 88 80 01 00 00 00 00 00 71 71 00 09

but it only works with driver ifdokrfid_lnx_x64-2.10.0.1 and both NFC and 
contact modes fail with driver ifdokrfid_lnx_x64-2.11.0.

Have you a special /etc/cmrfid.ini file ?

It is true that the issue appeared after upgrading from Ubuntu 13.04 to 13.10.

Nevertheless, the reader is reading with the contact interface a banking card 
(with the EMV script). Thus I suspect the driver to have difficulties to handle 
the korrigo card and probably this is not an issue related to cardpeek.

Original comment by [email protected] on 29 Nov 2013 at 9:11

[GoogleCodeExporter]

I don't have a special /etc/cmrfid.ini file. However, I know that Omnikey 
drivers are strange… I've had similar problem with debian in the past. As far 
as I remember in some cases, some cards work better with the "non proprietary" 
driver in contact mode.

I'll close this bug for now then.

Original comment by [email protected] on 5 Dec 2013 at 4:24

• Changed state: WontFix