Feeling my way into perso of a Visa applet and wanted a sanity check on approach and perhaps help to understand the result... #369
-
... I am hoping to use 'gptool' to load the visa applet and then in a separate invocation add DGI's for the Visa applet. First question first - is it actually viable to use as multiple invocations of gptool or is incorrect? My current invocations of gptool are to :-
These two steps look to complete fine, but when I then try to use -store-data-chunk using
Please note:-
The sanity checks I am seeking to make here are :
If the above all seems fine to you the reader, then any guidance on helping me to understand my 0x6A88 result on the first STORE would be appreciated. I have attached the --list output of the javacard before the --store-data-chunk attempt :- and the output from the --store-data-chuck command :- output_from_STORE-DATA-CHUNK_attempt.txt The javacard I have chosen to use here is an 'NXP J3H145 Dual Interface Java card - 144k'. If I have missed sharing something important for you then please say I will try and fill any gaps I need to. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Having slept on this overnight, I spent needed time assessing the parameters and the data being written to the card. I found my error. In my store-data-chunk payload I was erroneously including the STORE_DATA command header. This command and length detail was being added as well by gptool causing the card to see the STORE_DATA command as the DGI bytes and rejecting it. For clarity, I was specifying :- and I should (of course) have been just specifying the data I wanted to store :- --store-data-chunk 92071882022000940818030301100203009F100706011103000000 and having gptool wrap it perfectly for me. So In summary, my approach of using separate invocations of gptool seems ok and now my parameters into it are correct, I am moving forward again. |
Beta Was this translation helpful? Give feedback.
Having slept on this overnight, I spent needed time assessing the parameters and the data being written to the card. I found my error. In my store-data-chunk payload I was erroneously including the STORE_DATA command header. This command and length detail was being added as well by gptool causing the card to see the STORE_DATA command as the DGI bytes and rejecting it.
For clarity, I was specifying :-
--store-data-chunk 80E200011B92071882022000940818030301100203009F100706011103000000
and I should (of course) have been just specifying the data I wanted to store :-
--store-data-chunk 92071882022000940818030301100203009F100706011103000000
and having gptool wrap it perfectly for me.
So In sum…