PSSI should check smart card plugin compatibility with ATR

[GoogleCodeExporter]

Each type of smart card has a dedicated and (almost) unique ATR that can be 
used to identify the smart card. The pcsc-tools project has a list here: 
http://ludovic.rousseau.free.fr/softwares/pcsc-tools/smartcard_list.txt

I suggest to add a getATR() function in plugin.py that returns a list of ATR to 
identify the compatibles smart cards. If the inserted smart card has an ATR 
that doesn't match, PSSI shouldn't try to read the smart card with that plugin.

Original issue reported on code.google.com by laurent.leonard.openminds@gmail.com on 27 Dec 2010 at 3:37

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Good point. I don't know how we should handle this though. 

I'm not sure pssi should absolutely forbid a user to use a plugin if the ATR is 
outside the expected range. 

There are several ways to go about this: 
- just print a warning and try to dump,
- require that a certain command line option (-f "force") is activated.

Another thing we could do is automatically detect what plugin to use just by 
looking at the ATR. That would be pretty cool: just insert your card, launch 
pssi without any argument, and then the magic happens.

Original comment by julien.f...@gmail.com on 2 Jan 2011 at 3:39

[GoogleCodeExporter]

I'm fine with a -f option to force ATR check, but we can show a warning message 
in this case if the ATR doesn't match with the specified plugin.

Really, automatic detection would be pretty cool !

Original comment by laurent.leonard.openminds@gmail.com on 2 Jan 2011 at 5:45