> If you have a card that goes havoc to random commands, you should take
> *extra*care* with this card. Like not use it at all.

lol

> Nevertheless, it would be nice to have a listing of readers and their
> properties (pinpad, contactless etc) but I also have little hope for a
> PC/SC workgroup change and wide-spread adoption in the close future...

I trust in you to make i possible (+Viktor +Ludovic). :P

>if you send a select apdu (00A4) there is little chance to destroy anything with real cards

What i am actually doing. i just give an example.

> -the meaningful bit is the application, not the container, this is more and more
> true with loadable objects, such as javacards and nfc phones. Two objects  can
> have totally different ATRs and still host the exact same application.

Thats the problem i had.

> So if anyone is designing a card recognition application, he should just avoid
> the atr. The fact that MS did it is not a good reason :)

In fact, for me, its a good reason not to use it.
:D

_______________________________________________
Muscle mailing list
Muscle@list...
http://lists.drizzle.com/mailman/listinfo/muscle