-
Notifications
You must be signed in to change notification settings - Fork 44
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
Add support for custom AID when running AlgTestJClient #185
Comments
Hi Brian, |
As a sidenote - all Fidesmo devices are already in the comparison matrix and the chips are publicly known (have a look here for example: https://github.com/fidesmo/fdsm/blob/master/src/main/java/com/fidesmo/fdsm/FidesmoCard.java#L67) |
A new package/application AID is made for each applet. The AID is composed of a fixed prefix, vendorassigned application id, and user chosen suffix. ( I'm not quire sure how to translate the static profiels that @martinpaljak provided into entries in the results matrix. I see a lot of entries for various NXP chips, but not sure what specific entry corresponds to the Fidesmo reference card or the VivoKey, |
The reference card is JCOP 2.4.2 R2 |
I would like to use this to test the capabilities of Fidesmo devices. Specifically, the Fidesmo reference card, and the human-implantable VivoKey (currently in beta).
Fidesmo is a kind of a Google Play for JavaCard applets. In order to install an applet onto a Fidesmo card, the developer must use a pre-configured AID provided by Fidesmo.
I was able to use Fidesmo's tools to compile AlgTest_JavaCard to a
.cap
file using the Fidesmo supplied AID and then load it on a Fidesmo card. However, it appears that the application ID is hard-coded intoJCAlgTest/AlgTest_JClient/src/algtestjclient/CardMngr.java
Lines 125 to 131 in 42abaaa
I tried changing the AID and building the client using the supplied ant configuration, but ran into ~100 compiler errors for missing symbols (many related to unit testing). I'm using IntelliJ and don't have enough experience (or time) to try and setup a working build envrionment based on the Ecliplise project properties.
The text was updated successfully, but these errors were encountered: