Incorrect parameters in APDU with Oberthur IAS-ECC card #2052
Comments
|
I find this part suspicious:
You say your card is oberthur, but Gemalto version is matched for some reason. From there on, the errors could be expected it looks like wrong card is assumed. But I did not check the code nor I have this card so I can not debug it myself. But I hope it could let you move forward. |
|
thanks @Jakuje, I'm gonna look this direction :) |
|
Hello @Jakuje, I just found where it came from based on your advice... The ATR of the card is : Moreover, I also have in my possession a true Gemalto IAS/ECC card: it has the same ATR and is recognized by OpenSC without any problem. Two extra questions if you have any clue :
|
|
The way I read that ATR match rule, it will match any ATR of the same length with 70 14 in the 11 and 12 bytes. That in not specific enough and can easily falsely match other cards too. Cards these days can be loaded with various applets, without changing the ATR. Just checking for an ATR is not good enough, the present of the applet needs to be checked too. Oberthur cards are also used for CAC and PIV cards too. It sounds like the "IAS/ECC Gemalto" driver need to do a better job in identifying its applet. It should be checking for an AID as part of the match as many other drivers do. You can also change the order of the drivers to avoid |
|
|
|
Hi @dengert, If my understanding is good, I have to force the use of "IAS/ECC Oberthur" driver. |
|
My thinking, is you got a "Oberthur dual ID One Cosmo" card" and are assuming it already has an ISA/ECC applet on the card for some reason. Where did you get the card? If it does not say IAS/ECC then maybe is is just an Oberthur dual ID One Cosmo with no special applet on it yet. Google for: Oberthur dual ID One Cosmo profile "A05" |
|
Thanks @dengert, it was a mistake, the card model that was provided to me was wrong. So this card is effectively a Gemalto one but seems not to be working with OpenSC. The provider tells me it supports middleware ANTS IAS-ECC v2 only. So sad. |
DBarthe
changed the title
|
I'll try to figure out why this card is not working properly with the vendor and I'll post anything new here. Feel free to close the issue if you think the problem is not OpenSC side. |
DBarthe
changed the title
DBarthe
changed the title
|
Hello here :) I have some news from the vendor. This card is effectively Oberthur IAS-ECC but has the same ATR as Gemalto IAS-ECC card, and this is normal... Below is a screenshot of the same card loaded with IDopte middleware (in french)
Digging deeper into IAS-ECC middleware/card compatibility, I'm starting to think that the interoperability of IAS-ECC is something very theoretical. For instance, Gemalto IAS-ECC cards work well with ANTS middleware v2 et v3 (Gemalto actually wrote the middleware for the french agency ANTS), while Oberthur IAS-ECC works partially and only with ANTS middleware v2. Oberthur IAS-ECC should then work well with Oberthur middleware AWP... but I can't get a proper copy of it. However, I know very little about the internals of smart cards. |
|
I am prepared to investigate this, but in order to do that a test card is needed. Are there any test cards available for order? (Paying is not a problem). |
|
Hi all, are there any updates on this issue? I'm having the same problem with a belgian eID card v1.8 which seems the same card. |
Problem Description
Hello,
I've been trying to make OpenSC works with IAS-ECC card Oberthur dual ID One Cosmo profile A05, but never succeed so far. (this one I guess)
This card model seems to be supported according to the wiki except it is not explicitly mentioned "dual" (with contactless support).
Steps to reproduce
The command
opensc-tool --namefails with this error message :I'm not familiar with APDU :'-(
Logs
I put the full log here for compactness (sorry it's more than 10 lines...).
Extra information
I've also got different issues with this same card using other middleware.
With ANTS v2.x, the middleware would hang while listing slots.
With ANTS v3.2 the middleware would login and read the card with success but would fail when writing any object (typically CKR_DEVICE_ERROR).
With AWP 4.4 (an unofficial version found on the net), it would fail when writing any object saying the user is not logged in, except it is.
I've been using the same piece of software with other cards and it worked like charm.
Is there anyone experimented with smart card that could help me figure out something ? :)
The text was updated successfully, but these errors were encountered: