Hi Ludovic,

Thank you very much for your help.

> It surprise me. This missing "/" bug was corrected before the 1.2.0
> release. See [1] for the patch. Can you remove your installed pcsc-lite
> and install an _official_ 1.2.0 version ?

In hotplug_linux.c line 129, it needs a slash.  Pls check.

> I also see:
>> hotplug_linux.c:179 Disabling USB support for pcscd
>
> So I imagine your GemPC Twin is _not_ USB but connected to a serial
> port. Right?

Yes, I used the serial port instead of USB.  Does it make any difference?

>> But what is the reason of "commands.c:335 Procedure
>> byte conflict"?
>
> This error message occurs when you use a T=1 card in TPDU mode. This is
> not supported in libccid 0.3.2 (I am working on it). And your card is a
> T=1 card (according to the ATR).

I already commented the "#if 0" and "#endif" in ccid-0.3.2/src/ccid.c.  But
when I try to format the token, I got the "Formatting token [***] : Failed
(Unknown SW: 6F00)" message.  But I can CONNECT the token after that, and
cannot verify the PIN.  Pls see following log.

> How did you load the applet? Using this reader under GNU/Linux? Using
Windows?
Because I could not load the applet under Linux due to missing a libjct.so
in IBM JCOP Tools 2.2, I loaded the applet by using MicroExperts'
jcop-musclecard under Windows.

Thank you very much again.

Bo Wu

ifdhandler.c:320 entering IFDHPowerICC (lun: 0)
eventhandler.c:466 EHSpawnEventHandler: Card inserted into Generic Reader 0
0
EHSpawnEventHandler: Card ATR: 3B E6 00 FF 81 31 FE 45 4A 43 4F 50 30 33 07
winscard_msg.c:250 SHMProcessEvents: Common channel packet arrival
pcscdaemon.c:144 SVCServiceRun: Client 8 has disappeared.
winscard_msg.c:289 SHMProcessEvents: correctly processed client: 0
winscard.c:80 SCardEstablishContext: Establishing Context: 16987629
winscard_msg.c:289 SHMProcessEvents: correctly processed client: 0
winscard.c:149 SCardConnect: Attempting Connect to Generic Reader 0 0
winscard.c:245 SCardConnect: Active Protocol: 2
winscard.c:252 SCardConnect: hCard Identity: 1a552
winscard_msg.c:289 SHMProcessEvents: correctly processed client: 0
winscard_msg.c:289 SHMProcessEvents: correctly processed client: 0
winscard.c:1293 SCardTransmit: Send Protocol: 1
APDU: 00 A4 04 00 06 A0 00 00 00 01 01
ifdhandler.c:416 entering IFDHTransmitToICC (lun: 0)
SW: 90 00
winscard_msg.c:289 SHMProcessEvents: correctly processed client: 0
winscard.c:1293 SCardTransmit: Send Protocol: 1
APDU: B0 2A 00 00 38 08 4D 75 73 63 6C 65 30 30 04 01 08 30 30 30 30 30 30
30 30
 08 30 30 30 30 30 30 30 30 05 02 08 30 30 30 30 30 30 30 30 08 30 30 30 30
30 3
0 30 30 00 00 1B B8 00 02 01
ifdhandler.c:416 entering IFDHTransmitToICC (lun: 0)
SW: 6F 00
winscard_msg.c:289 SHMProcessEvents: correctly processed client: 0
winscard.c:641 SCardDisconnect: Active Contexts: 1
ifdhandler.c:320 entering IFDHPowerICC (lun: 0)
winscard.c:703 SCardDisconnect: Reset complete.

#######################################################

muscle > tokens
   1.    IBM JCOP 30

muscle > format 1
Would you like to:
 1. Use the default factory key: 2C15E526E93E8A19
  2. Use the MUSCLE default key : 4D7573636C653030
 3. Enter your own transport key

Choose (1-3): 2

How much object memory would you like to allocate ?
Example: 7096 (7k) : 7096
Please enter a new auth pin value (pin 0) : 00000000
Please enter your user pin value (pin 1)  : 00000000
Please enter your user pin unblock value  : 00000000
Please enter your number of pin tries     : 5

********************* WARNING ! *********************
You are about to destroy all data on this token.
*****************************************************

Current admin pin      : Muscle00
New admin pin          : 00000000
New user pin           : 00000000
New user unblock pin   : 00000000
Number of tries        : 5
Object memory          : 7096

Are you sure you want to continue ? (1-YES, 2-NO): 1

Formatting token [***] : Failed (Unknown SW: 6F00)
muscle > muscle >



_______________________________________________
Muscle mailing list
[EMAIL PROTECTED]
http://lists.musclecard.com/mailman/listinfo/muscle

Reply via email to