Re: MUSCLE VerifyKey using OCF

[Emiliano Ida']

 Hi All,
 
 Does anybody here use Cyberflex Access cards with OCF?
 
 If so, could you help me with the doubt below?
 
 In the Cyberflex Access card we have the idea of identity such as AUT0,
 AUT1, etc. In OCF to verify a Card Holder we must use the sendVerifyCommand.
 Now what do I do to verify a identity using OCF?? In CyberflexAccess we have
 the VerifyKey command (00, 2A, 00, Key_NUMBER, Len, Key).

Hi,
To do so, you can build a CardService containing these two functions:


private ResponseAPDU sendAPDU(byte apdu[]) throws CardTerminalException {
CommandAPDU commandAPDU = new CommandAPDU(apdu);
System.out.println(commandAPDU);
ResponseAPDU responseAPDU = getCardChannel().sendCommandAPDU(commandAPDU);
System.out.print(Status Word: + Integer.toHexString(responseAPDU.sw())+\n);
return (responseAPDU);
}


public void verifyKey() {
byte[] verapdu = //a byte array containing (00, 2A, 00, Key_NUMBER, Len, Key)
ResponseAPDU resapdu;
try {
allocateCardChannel();
resapdu = sendAPDU(verapdu);

} catch (Exception e) {e.printStackTrace();
} finally {releaseCardChannel();}   
}
 

Hope this helps,
Emiliano Ida'
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***

MUSCLE Cyberflex Access IC

[Emiliano Ida']

Hi,
i need to know some information about the IC used by Cyberflex Access:
-manufacturer of the chip.
-type of the chip.
-(eventually) some datasheet about the performance of the cryptographic
functions.
Excuse me if this argument is (maybe) a little bit off-topic.
Thanking you in advance,
Emiliano Ida'
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***

Re: MUSCLE pcsc problem?

[Emiliano Ida']

Hi,

 0x77 is not a valid sw1.  Read up on 7816-3.
I experience the same error using a SW 0x6F00, that should be a valid SW.

 However, I think you are solving the timeout problem the wrong way.  Your
 applet should stall by sending nulls (0x60) until it is ready with the
 reply.  You do this by calling apdu.waitExtension().  You may also have to
 change the protocol bytes in your atr to give the card a longer wwt.

Yes, i tried these two solutions before, but there were some problems:
1) calling apdu.waitExtension seems does not have effect, even if i call it
very very frequently
2)The version of slb-rf60 driver doesn't look at ATR for timeout.

Many thanks for your help. Sincerely,
Emiliano Ida'
***
Linux Smart Card Developers - M.U.S.C.L.E.
(Movement for the Use of Smart Cards in a Linux Environment)
http://www.linuxnet.com/smartcard/index.html
***