reader capabilities

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

reader capabilities

J.Witvliet

Hi all,

 

Is there a way to find out the capabilities of the card-readr currently attached to a system?

Mainly if it is a class-1, class-2 or class-3 device?

 

Up till now, I have mainly worked with simple class-1 reader.

Within my scripts I prompt for the PIN, and cache it.

 

Obviously that does not work for pin-pad-readers, so I should treat them differently, but how can I tell the difference?

 

Hans

 


Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
Reply | Threaded
Open this post in threaded view
|

Re: reader capabilities

Ludovic Rousseau
2014-10-10 15:01 GMT+02:00  <[hidden email]>:
> Hi all,
>
>
>
> Is there a way to find out the capabilities of the card-readr currently
> attached to a system?

Yes, sure.

> Mainly if it is a class-1, class-2 or class-3 device?

You can know if the reader + driver supports FEATURE_VERIFY_PIN_DIRECT.

You can know if the reader has a display screen using
PCSCv2_PART10_PROPERTY_wLcdMaxCharacters and
PCSCv2_PART10_PROPERTY_wLcdMaxLines.

> Up till now, I have mainly worked with simple class-1 reader.
>
> Within my scripts I prompt for the PIN, and cache it.
>
>
>
> Obviously that does not work for pin-pad-readers, so I should treat them
> differently, but how can I tell the difference?

Use PC/SC v2 part 10 document. See scardcontrol.c [1] for a sample
program using PC/SC v2 part 10.

Bye

[1] http://anonscm.debian.org/viewvc/pcsclite/trunk/Drivers/ccid/examples/scardcontrol.c?view=markup

--
 Dr. Ludovic Rousseau

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
Reply | Threaded
Open this post in threaded view
|

Re: reader capabilities

J.Witvliet
In reply to this post by J.Witvliet
Thank you very much!

-----Original Message-----
From: Ludovic Rousseau [mailto:[hidden email]]
Sent: vrijdag 10 oktober 2014 15:22
To: Witvliet, J, DMO/OPS/I&S/HIN
Cc: [hidden email]
Subject: Re: [Opensc-devel] reader capabilities

2014-10-10 15:01 GMT+02:00  <[hidden email]>:
> Hi all,
>
>
>
> Is there a way to find out the capabilities of the card-readr
> currently attached to a system?

Yes, sure.

> Mainly if it is a class-1, class-2 or class-3 device?

You can know if the reader + driver supports FEATURE_VERIFY_PIN_DIRECT.

You can know if the reader has a display screen using PCSCv2_PART10_PROPERTY_wLcdMaxCharacters and PCSCv2_PART10_PROPERTY_wLcdMaxLines.

> Up till now, I have mainly worked with simple class-1 reader.
>
> Within my scripts I prompt for the PIN, and cache it.
>
>
>
> Obviously that does not work for pin-pad-readers, so I should treat
> them differently, but how can I tell the difference?

Use PC/SC v2 part 10 document. See scardcontrol.c [1] for a sample program using PC/SC v2 part 10.

Bye

[1] http://anonscm.debian.org/viewvc/pcsclite/trunk/Drivers/ccid/examples/scardcontrol.c?view=markup

--
 Dr. Ludovic Rousseau

______________________________________________________________________
Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen. De Staat aanvaardt geen aansprakelijkheid voor schade, van welke aard ook, die verband houdt met risico's verbonden aan het electronisch verzenden van berichten.

This message may contain information that is not intended for you. If you are not the addressee or if this message was sent to you by mistake, you are requested to inform the sender and delete the message. The State accepts no liability for damage of any kind resulting from the risks inherent in the electronic transmission of messages.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensc-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/opensc-devel