On 24/05/2012 15:39, Martin Paljak wrote: >> Too bad the cards aren't recognized by default: >> $ opensc-tool -a -n >> Using reader with a card: ACS ACR122U PICC Interface 00 00 >> 3b:85:80:01:4d:79:45:49:44:78 >> Unsupported card > I'm not certain about all ACS products, but one of the 122 reader > marketed as tikitag/touchatag is CCID, but it requires a special APDU > wrapping to actually talk to the RF interface. Maybe this reader is > similar. I think this one is well supported: its driver sources have 'rousseau' in nearly all headers :) Seems Ludovic got a contract with ACS (I hope for him) in 2009...
If I insert one of the cards in the contact reader, I get the same ATR as standard MyEID cards: $ opensc-tool -a -n Using reader with a card: Gemalto GemPC Twin 00 00 3b:f5:18:00:00:81:31:fe:45:4d:79:45:49:44:9a MyEID cards with PKCS#15 applet But (obviously) if I place it on NFC reader I can't use it: $ pkcs15-init -C --pin 1111 --puk 1111 Using reader with a card: ACS ACR122U PICC Interface 01 00 Couldn't bind to the card: Not supported Is there any way I could "force" pkcs15-init in recognizing it as myeid (like "-c myeid" for pkcs11-tool)? BTW for the other ATR (3b:8f:80:01:80:4f:0c:a0:00:00:03:06:03:00:01:00:00:00:00:6a) I already found: it's a Mifare One card (just tested with others I had around). BYtE, Diego. _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
