Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Can I implement the Authenticate Command from PC/SC Specifications Part 3 for Java OpenCard framework?

0
Posted

Can I implement the Authenticate Command from PC/SC Specifications Part 3 for Java OpenCard framework?

0

Yes, the Authenticate Command was redefined in PC/SC Specification Part 3 v.2.01.09. Just make certain you are not using an older version of the Specification. • We are testing for T=1 protocol uning INFINEON test cards and unfortunately we don’t have enough test data to confirm our hardware. The SELECT Command and the value is different for T=0 protocol. There is a fundamental difference between T=0 and T=1 cards. T=0 cards accept TPDU’s (CLA, INS, P1, P2, P3…); T=1 cards accept only APDU’s (CLA, INS, P1, P3, Lc, Data, Le). The TPDU level of communication isn’t there (see ISO 7816-3 for how to map TPDU’s to APDU’s). For more information, please refer to the official Sicrypt home page www.sicrypt.com and visit their downloads area of the website. • I do not understand the extended length suupprted by SICRYPT card. Can you give lme more details on this? The SICRYPT card supports “Extended Length” according to ISO 7816-3 (Case 2E/3E/4E command/response pairs). The coding itself is supp

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123