Hi Steve,

Yes, the applet will do that until you format the token. Unfortunately, I just checked the protocol documents and that is not documented. I'm attaching a code piece from the MCardPlugin to hopefully map it out though:

B0 2A 00 00 LEN

Data:

Type Le Value

TransportKeyLength 1 8
Transport Key 8 Muscle00
TransportKeyTries 1 5
UnblockKeyTries 1 3
NewTransportLen 1 8
NewTransportKey 8 whatever you want
NewUnblockLen 1 8
NewUnblockKey 8 whatever you want
UserPinTries 1 5
UserUnblockTries 1 3
UserPinLen 1 8
UserPin 8 whatever you want
UserUnblockLen 1 8
UserUnblock 8 whatever you want
Object Memory 4 8096 00000000 00001FA0
CreateObjACL 1 00 (anyone can create)
CreateKeysACL 1 02 (pin 1 required)
CreatePINsACL 1 01 (pin 0 required)


Hope this helps ...

Dave







On Jan 26, 2004, at 6:56 PM, Steve Leung wrote:

I've installed Muscle Applet 0.9.10 into a Cyberflex Access 32K developer card using Cyberflex SDK toolkit.
I was able to instantiate the Muscle applet and selected it as the default applet in Cyberflex SDK toolkit.
However, whenever I use the APDU manager in the toolkit to send APDU command to the applet, I always get 9C05 as return code (SW_UNSUPPORTED_FEATURE).

Like VerifyPin:
B0 42 00 00 08
4D 75 73 63 6C 65 30 30

I only get 9C05 back as return code.

Did anyone come accross this problem before ??
Any advice will be greatly appreciated.

__________________________________________________________________
New! Unlimited Netscape Internet Service.
Only $9.95 a month -- Sign up today at http://isp.netscape.com/register
Act now to get a personalized email address!

Netscape. Just the Net You Need.
_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle


<x-tad-bigger>*****************************************************************************
David Corcoran <[EMAIL PROTECTED]>
Identity Alliance [http://www.identityalliance.com]
Smart Cards, Biometrics, Training, Identity Management
*****************************************************************************
</x-tad-bigger>

Reply via email to