Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support PC/SC v2 and improve reader model identification #9

Open
Maxhy opened this issue May 6, 2013 · 1 comment
Open

Support PC/SC v2 and improve reader model identification #9

Maxhy opened this issue May 6, 2013 · 1 comment
Labels
enhancement

Comments

@Maxhy
Copy link
Member

Maxhy commented May 6, 2013

Some parts of PC/SC v2 should be implemented to better identify a PC/SC reader model.
See

http:https://ludovicrousseau.blogspot.fr/2011/11/identifying-reader-model.html
http:https://ludovicrousseau.blogspot.fr/2012/04/identifying-reader-model-part-2.html
@Maxhy
Copy link
Member Author

Maxhy commented May 30, 2013

PC/SC part10 v2 Windows implementation doesn't support TLV properties yet.
Need an update on Windows SDK to add this features, or add temporary the defines into liblogicalaccess.

xaqq added a commit that referenced this issue Dec 9, 2015
@xaqq
Add a PCSCFeatures class that can extract information from a reader
c788109 
This helper class works with a PCSCConnection as input.
It can retrieve the list of enabled feature on the reader, and
extract TLV Properties from the reader, if applicable.

This is work towards #9
xaqq added a commit that referenced this issue Feb 1, 2016
@xaqq
Add a PCSCFeatures class that can extract information from a reader
4eba28a 
This helper class works with a PCSCConnection as input.
It can retrieve the list of enabled feature on the reader, and
extract TLV Properties from the reader, if applicable.

This is work towards #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Maxhy