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.

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

Get some flexibility in the tag type detection #17

Open
GoogleCodeExporter opened this issue Mar 12, 2015 · 0 comments
Open

Get some flexibility in the tag type detection #17

GoogleCodeExporter opened this issue Mar 12, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

Currently an internal table helps guessing the type of tag based on its SAK & 
ATS.
But now phones start being able to emulate tags (CyanogenMod, Kitkat,...) while 
SAK & ATS are still not under control, so being different than expected.

How to get more flexibility?

Getting an environment variable to bypass entirely detection and assume that 
we've a tag of the right type requested by the application?

Or instead of guessing the tag from its SAK/ATS, test proactively if the tag is 
of a specific type?

E.g. ASSERT_MIFARE_DESFIRE(tag) would not check a preset flag but would test 
actively if the card is a DESFIRE by sending a GetInfo command.

Original issue reported on code.google.com by yob...@gmail.com on 3 Dec 2013 at 3:23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant