you know how I can fix this?
is there a source file that i can make the necesary changes in to try
out your idea?

also would this prohibit me from sending standard crytoflex APDU's to
the card through an interface such as scriptor or gscriptor?
If I can still send APDU's, I was wondering what the sequence of the
APDU's would be. I think the first thing I need to do is authenticate
myself to the card and unlock some of the other commands using the
transport key. I am unsure if I would use the VERIFY_KEY APDU or the
EXTERNAL_AUTHENTICATION APDU for this. Next would I try to use the
VERIFY_CHV with a PIN number?

Thanks
dsk

* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2003-10-22 20:05]:
> Date: Wed, 22 Oct 2003 21:29:27 +0200
> From: Damien Sauveron <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: [Muscle] SLB Cryptoflex Connection Problems
> Reply-To: [EMAIL PROTECTED]
> 
> Hi,
> 
> First, I am not a specialist of Muscle but  I have the feeling that the problem 
> provides from the 
> reflex driver.
> It seems that it doesn't chain the GET_RESPONSE on the 61XX (here 6114 in the pcscd 
> log ). 
> And I think that this causes the "> musclecard.c:497 MSCIdentifyToken returns Object 
> not 
> found".
> 
> I don't think that the AID is the problem but I have never used a cryptoflex.
> 
> Regards,
> 
> Damien Sauveron
> 
> 
> > Hello all,
> > 
> > I recently received a Schlumberger Reflex USB reader (ver.1) and 32K
> > Cryptoflex card for development and I am having a problem using the
> > muscleTool application to connect to the card. 
> > 
> > I am running Debian on both of the machines I tried.
> > I first installed the following Debian Packages
> > 
> > pcscd
> > pcsc-tools
> > libpcsclite0
> > muscletools
> > libmcardplugin
> > libcflexplugin
> > (i think thats it)
> > 
> > Next I ran the bundleTool application and that was successful, 
> > I've tried it with options 1 and 2, 
> > 
> > -----start - terminal - shot -----
> > sunshine:/home/derrick# bundleTool 
> > Select the approprate token driver:
> > -----------------------------------
> >   1.     slbCryptoflex.bundle
> >   2.     mscMuscleCard.bundle
> > -----------------------------------
> >   Enter the number: 2
> > 
> > Insert your token in: Reflex USB 0 0
> > 
> > Token support updated successfully !
> > -----end - terminal - shot -----
> > 
> > After that I run the muscleTool application. Running the 'tokens'
> > command gives the following output
> > 
> > 
> > -----start - terminal - shot -----
> > sunshine:/home/derrick# muscleTool 
> > 
> > MuscleCard Shell - type help for help
> > 
> > muscle > tokens
> > tokenfactory.c:194 ATR comparison: FILE: 
> >   /usr/lib/pcsc/services/slbCryptoflex.bundle/Contents/Info.plist
> > 
> > tokenfactory.c:195 ATR comparison: Target Match: 3B951840FF6201020104
> > 
> > tokenfactory.c:208 ATR comparison: Source: 3B951840FF6201020104
> > 
> > tokenfactory.c:220 Match found at ATR alias 0
> > 
> > tokenfactory.c:243 Product name: SchlumbergerSema Cryptoflex
> > 
> > tokenfactory.c:352 No AID specified in bundle
> > 
> > tokenfactory.c:194 ATR comparison: FILE: 
> >   /usr/lib/pcsc/services/slbCryptoflex.bundle/Contents/Info.plist
> > 
> > tokenfactory.c:195 ATR comparison: Target Match: 3B951840FF6201020104
> > 
> > tokenfactory.c:208 ATR comparison: Source: 3B951840FF6201020104
> > 
> > tokenfactory.c:220 Match found at ATR alias 0
> > 
> > tokenfactory.c:243 Product name: SchlumbergerSema Cryptoflex
> > 
> > tokenfactory.c:352 No AID specified in bundle
> > 
> >    1.    SchlumbergerSema Cryptoflex
> > 
> > muscle >
> > 
> > -----end - terminal - shot -----
> > 
> > I'm not sure what the last line from tokenfactory.c means 
> > tokenfactory.c:352 No AID specified in bundle
> > 
> > Is this something to worry about? 
> > Do I need to change a configuraion file somewhere?
> > 
> > Lastly I try to use the 'connect 1' command to connect to the token that
> > was generated by bundleTool. This is not successful
> > 
> > 
> > -----start - terminal - shot -----
> > 
> > muscle > connect 1
> > musclecard.c:350 SCardConnect returns Command successful.
> > 
> > musclecard.c:383 SCardStatus returns Command successful.
> > 
> > tokenfactory.c:194 ATR comparison: FILE: 
> >   /usr/lib/pcsc/services/slbCryptoflex.bundle/Contents/Info.plist
> > 
> > tokenfactory.c:195 ATR comparison: Target Match: 3B951840FF6201020104
> > 
> > tokenfactory.c:208 ATR comparison: Source: 3B951840FF6201020104
> > 
> > tokenfactory.c:220 Match found at ATR alias 0
> > 
> > tokenfactory.c:243 Product name: SchlumbergerSema Cryptoflex
> > 
> > tokenfactory.c:352 No AID specified in bundle
> > 
> > tokenfactory.c:437 Loading service library 
> > /usr/lib/pcsc/services/slbCryptoflex.bundle/Contents/Linux/slbCryptoflex
> > 
> > musclecard.c:425 TPLoadToken returns Command successful.
> > 
> > musclecard.c:497 MSCIdentifyToken returns Object not found
> > 
> > ERR: EstablishConnection Failed !muscle > 
> > 
> > -----end - terminal - shot -----
> > 
> > 
> > here is the output from pcscd -f -d stderr
> > 
> > -----start - terminal - shot -----
> > 
> > bash-2.05b$ pcscd -f -d stderr
> > pcscdaemon.c:256 main: pcscd set to foreground
> > pcscdaemon.c:265 main: debug messages to stderr
> > pcscdaemon.c:473 main: pcsc-lite daemon ready.
> > hotplug_libusb.c:343 Adding USB device: 001:015
> > readerfactory.c:1319 RFInitializeReader: Attempting startup of Reflex
> > USB 0 0.
> > readerfactory.c:1061 RFBindFunctions: Loading IFD Handler 2.0
> > winscard_msg.c:263 SHMProcessEvents: Common channel packet arrival
> > winscard.c:81 SCardEstablishContext: Establishing Context: 17000669
> > winscard.c:149 SCardConnect: Attempting Connect to Reflex USB 0 0
> > winscard.c:245 SCardConnect: Active Protocol: 1
> > winscard.c:252 SCardConnect: hCard Identity: 11b5a
> > winscard.c:1293 SCardTransmit: Send Protocol: 0
> > T=0 -> c0 a4 0 0 2 3f 0 
> > Length to send is 2
> > T=0 <- 61 14 
> > winscard.c:1293 SCardTransmit: Send Protocol: 0
> > T=0 -> c0 a4 0 0 2 3f ce 
> > Length to send is 2
> > T=0 <- 6a 82 
> > winscard.c:642 SCardDisconnect: Active Contexts: 1
> > 
> > -----end - terminal - shot -----
> > 
> > Anyone have an idea of what maybe causing the connection error?
> > Any help is appreciated 
> > 
> > Thanks In Advance
> > derrick
> > 
> > _______________________________________________
> > Muscle mailing list
> > [EMAIL PROTECTED]
> > http://lists.musclecard.com/mailman/listinfo/muscle
> > 
> 
> 
> 
> 
> -------------------------------------------------
> This mail sent through IMP: http://horde.org/imp/

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

Reply via email to