Forum Replies Created
Re: Reply To: Looking for partner or consultant for a Micropayment Project9. April 2017 at 12:32 in reply to: Looking for partner or consultant for a Micropayment ProjectHi Emad
You can reach me on firstname.lastname@example.org
+ 0 | - 0
Re: Reply To: use of SAM based hardware keystore with TapLinx and Desfire EV14. November 2016 at 10:13 in reply to: use of SAM based hardware keystore with TapLinx and Desfire EV1
I suggest following design. This will work with any SAM hardware reader and will work with Spongy Castle too.
Talking to the SAM reader.
Please defined a callback function with clear defined interface. This function will be called by TapLinx SDK but should be implemented by the person implementing the SAM reader support , however the implementation should follow the interface defined by TapLinx SDK.
Talking to the Desfire card.
Please implement the authenticate API which can take encrypted data from the previous callback and talk to the Desfire card and complete authentication.
Changes needed to current authenticate API with SpongyCastle
Instead of passing the actual key in objKEY_2KTDES, you should pass encrypted data out of that key. This should be according to TalktoSAMReaderCallback defined earlier
It would look like this in code.
TalktoSAMReaderCallback(EncryptedDatafromSAM); /*This function should be implemented by the person implementing SAM reader. This should contain the SAM reader driver specific calls. The function after returning should populate EncryptedDatafromSAM with encrypted data returned by SAM.*/
AuthenticatewithDesfire(EncryptedDataFromSAM); /*This function should use EncryptedDataFromSAM as input and complete authentication protocol with Desfire card.*/
Let me know if these changes can be done in SDK APIs and any time frame for the release.
+ 0 | - 0
Re: Reply To: use of SAM based hardware keystore with TapLinx and Desfire EV11. November 2016 at 10:14 in reply to: use of SAM based hardware keystore with TapLinx and Desfire EV1
For USB/Bluetooth based SAM reader working on Non X Mode.
The below API will never work
desFireEV1.authenticate(0, IDESFireEV1.AuthType.Native, KeyType.THREEDES, objKEY_2KTDES );
Because objKEY_2KTDES contains the actual key.
Therefore, what is the sequence of TapLinx APIs I should call to authenticate using a USB/Bluetooh based SAM reader working in Non X Mode.
Can you suggest any commercially available USB/Bluetooth based SAM Reader which I can buy and experiment? I need to evaluate this for a commercial deployment of a TapLinx based Android reader for a finance application.
>>> Please have a look to SAM_AuthenticatePICC() (chapter 11.7.1). It is required to have the authentication key in SAM.
Which document are you referring to? and where do I get this document ? I already have a NDA signed with NXP. Can you request a FAE to reach me on my email id email@example.com
Can I send native commands to Desfire EV1 using the TapLinx APIs. If yes, which API should I use for this ? If no, then how will I be able to integrate with TapLinx any SAM Reader (USB based working in Non X Mode).
+ 0 | - 0
Viewing 3 posts - 1 through 3 (of 3 total)