Subject: Re: USB reader bundles don't work with PCSC Lite 1.1.1 on SuSE 8.1 - msg#00009

Previous Message by Date: click to view message preview

OpenSSL PKCS#11 Engine patch & MUSCLE

Hi, There is a PKCS#11 Engine patch for OpenSSL 0.9.7 (http://www.openca.org/news/). Did anyone got this working with the MUSCLE libraries (libpkcs11.so) ? Are there any other OpenSSL Engine patches for MUSCLE available ? Kind regards, /// wj --

Next Message by Date: click to view message preview

MacOSX cryptoflex 8k recognized as Egate 32 k

I am having problems with the Musclecard framework on Mac OS X. First I installed the framework, no problem. I install a Cryptoflex 16 k, and the card is recognized and I can format the card. Next I tried a Cryptoflex 8k. It was not recognized. So I used pcsctool to assign the card as a cryptoflex card: ======================================================================== == [albatros:~johanloc/Desktop] johanloc# pcsctool Select the approprate token driver: ----------------------------------- 1. commonAccessCard.bundle 2. mscMuscleCard.bundle 3. slbCryptoflex.bundle ----------------------------------- Enter the number: 3 Insert your token in: GemPC430 0 0 Token support updated successfully ! ======================================================================== == But after that action, the card is recognized as a Cryptoflex eGate. Actually, every Cryptoflex card after this update is recognized as a cryptoflex eGate. Here I inserted a crypoflex 16 K card: ======================================================================== == [albatros:~johanloc/Desktop] johanloc# muscleTool MuscleCard Shell - type help for help muscle > tokens 1. Cryptoflex eGate 32k muscle > ======================================================================== == I can even do stuff on it: ======================================================================== == muscle > connect 1 muscle [Cryptoflex eGate 32k] > verify 1 00000000 PIN Verify Successful muscle [Cryptoflex eGate 32k] > genkeys ***************** Key Generation Routine ***************** Note: Keys will be generated with default permissions using the RSA CRT algorithm for generation. ********************************************************** Enter the private key number: 1 Enter the public key number: 2 Are you sure ? (Y/N): Y Generating keys [******************] : Success muscle [Cryptoflex eGate 32k] > muscle [Cryptoflex eGate 32k] > list Object ID Object Size READ WRITE DELETE ----------------- ----------- ------ ------ ------ muscle [Cryptoflex eGate 32k] > listkeys Key Type Key Num SIZE READ WRITE USE ----------------- ----------- ----- ------ ------ ------ RSA PRIVATE CRT 1 1024 NEVER PIN #1 PIN #1 RSA PUBLIC 2 1024 ALWAYS PIN #1 PIN #1 ======================================================================== == So what is happening? Anybody an idea? Johan Henselmans PGP.sig Description: PGP signature

Previous Message by Thread: click to view message preview

Re: USB reader bundles don't work with PCSC Lite 1.1.1 on SuSE 8.1

Thanks for the tip. I recompiled the lot with the configuration option you mentioned but it doesn't seem to make a difference. I'll go through it with the debugger again this evening. What I don't understand is that regardless of USBDROPDIR I didn't encounter any code that tries to look for the bundles when I stepped through pcscd. On Thursday 06 February 2003 09:13, jipi wrote: > in some later versions of pcsclite it seems to have > "--enable-usbdropdir=/your/dir" as an configuration option. > > i remember using one of the previous versions. maybe 1.1.1, we need to > change this USBDROPDIR string constant (or is it?) in some .c file to > point to where your driver bundle is. > > do a grep for this on the source files and you might get some ideas. > > jipi > > bk390934@xxxxxxxxx wrote: > > Debugger: > > GNU dbg with the kdbg GUI (KDE desktop environment-. > > > > "configure" build options: > > > > --enable-usb \ > > --enable-debug \ > > --enable-utils \ > > --enable-syslog \ > > --enable-daemon \ > > --sysconfdir=%{_sysconfdir} > > > > On Thursday 06 February 2003 02:17, jipi wrote: > >>Just a curious question, what debugger are you using? > >> > >>And what options did u use if u compiled pcsc-lite-1.1.1 sources? > >> > >>jipi > >> > >>bk390934@xxxxxxxxx wrote: > >>>Thanks for the tip. I tried it but it didn't confirm whether the daemon > >>>actually searched for the bundles. > >>> > >>>When I use a debugger I noticed that the function > >>> HPSearchHotpluggables() is empty and simply returns . > >>> > >>>Ehm, bundles are not implemented yet or what? > >>> > >>>On Monday 03 February 2003 15:54, Gareth Bowker wrote: > >>>>Hi, > >>>> I've just started (today) using the ACS 30 and found your message > >>>> after finding the MUSCLE mailing list about an hour ago and looking > >>>> through the archive. Where, exactly, are you up to? > >>>> > >>>>I've managed to get the bundle picked up (by putting the directory > >>>>acsAcr30.bundle in /usr/local/pcsc/drivers). As I couldn't tell where > >>>> it was meant to go, I used strace to trace pcscd and find out where it > >>>> was looking. > >>>> > >>>>e.g. > >>>># strace /usr/local/sbin/pcscd -f -d stdout > >>>> > >>>>then search for all the open() calls. > >>>> > >>>>However, I'm now trying to work out how to get it to open the USB > >>>> rather than the serial. If anyone can help me out (or point me to the > >>>> code that deals with reader.conf) then I'd appreciate it. > >>>> > >>>>Thanks, > >>>> > >>>>Gareth > >>> > >>>_______________________________________________ > >>>Muscle mailing list > >>>Muscle@xxxxxxxxxxxxxxxxxxxx > >>>http://lists.musclecard.com/mailman/listinfo/muscle > >> > >>_______________________________________________ > >>Muscle mailing list > >>Muscle@xxxxxxxxxxxxxxxxxxxx > >>http://lists.musclecard.com/mailman/listinfo/muscle

Next Message by Thread: click to view message preview

Re: USB reader bundles don't work with PCSC Lite 1.1.1 on SuSE 8.1

Le vendredi 07 février 2003 à 02:09:38, Bart Symons a écrit: > What do you mean by "This is valid for pcsc-lite-1.1.2beta3 [1]. I do not > support older versions." I mean that I did not checked with older versions and I don't want to check older versions. You are free to use an older version if you want. But before sending a bug report check that the bug is not corrected in the latest version. Bye, -- Dr. Ludovic Rousseau Ludovic.Rousseau@xxxxxxx -- Normaliser Unix c'est comme pasteuriser le Camembert, L.R. --