Murilo,

Murilo Camões Perrone wrote:
> Karsten,
> 
> I have compiled libmusclecard, muscletool and mcardApplet.
> 
> Just in case you are courious about the results:

Thanks for the results.

>  - BundleTool can read the ATRs, but muscleTest can´t connect ( ERR:
> EstablishConnection Failed ! Is your card already formatted? ).

Well, is your card formatted? Have you installed the CardEdge applet and
run "format x" (x = Number of token)? I had no problems with this. At
least the last time, maybe I corrected something too good and now there
is a bug. But I have just tried with the version at the web location and
it works. Is the token recognized if you run the tokens command? Oh, I
guess I have the error ... At the moment the T=1 protocol is not
supported, because I have a card reader, with a broken T=1 protocol ...
just a moment ...

I corrected this. New versions of libmusclecard, MCardPlugin and Pkcs11
are at the web location

http://www.inf.tu-dresden.de/~ko189283/MuscleCard/

Now also your (I believe) T=1 card should work. Please try.

>  - I have tried with 3 different tokens and two different readers (CIS
> DT3500 USB and towitoko/chipdrive serial card readers).
>  - Is pkcs11 ready for w32 compilation ? I expected using it with mozilla
> browser, but it did not compile:
> 
>    c:\C\Muscle-win32\Pkcs11\src\p11x_object.c(859) : error C2039:
> 'cipherMode' : is not a member of 'MSCKeyPolicy'
>         c:\Program Files\Muscle\Includes\musclecard.h(500) : see declaration
> of 'MSCKeyPolicy'

I have not cared for Pkcs11 at the moment. This identifiers had to be
renamed to cipherSignatureMode and cipherCipherMode. I did this and sent
it in a private mail to you. You can ignore this. The version ate the
web location contains it. At least Thunderbird does not crash with the
module. Maybe it works ...

> Anyway, our CSP won´t use the pkcs11 module.
> 
> I noted some things:
> 
> - No muscletest windows executable was compiled. Maybe that´s because it
> depends on PC/SC Lite source files?

I have not examined this, but I think the truth is, that I did not
include it in the Makefile.

> - It looks like the DEBUG compilation is the default for all modules. Thasts
> ok.

Not, if you use nmake. Only if the switch DEBUG= is given to nmake the
DEBUG version is compiled. But this more convenient at the moment
because I/you can trace some commands with set MCARDPLUGIN_DEBUG=1.

> - Undocummented procedures are necessary, such as manually copying files
> into c:\program files\Muscle\...

In the Install.w32 everything is mentioned.

Also for libmusclecard. Where did I miss it? Apart from this the
location should be independent, because it searches in the registry for
the DropDir entry. But I noticed that this hint is missing in MCardplugin.

I updated the Install.w32 for MCardPlugin:

 4.     Copy the mscMuscleCard library from the Release or Debug directory
to the location
        mentioned in the registry at
HKEY_LOCAL_MACHINE\SOFTWARE\MUSCLE\MuscleCard.
        There you find the value for the entry DropDir. Create the directories
        mscMuscleCard.bundle\Contents\Win32 under this location and copy
mscMuscleCard into it.
        E.g. the default location is
        C:\Program Files\Muscle\Services\mscMuscleCard.bundle\Contents\Win32.


> 
> I´m using windows 2k and compiled everything specifying lpthreadsVC2 (not
> lpthreadsVC1).

I hope this does not matter. It should be fine.

> About ID Ally, we could not find a download for it or for the source code
> (looks like there was an open source code in past ?).
> I have sent email asking about it´s status.

Ask David. It should be at http://www.identityalliance.com/identity_ally.php

> 
> The idea of an separate makefile for windows seems good.
> 

Karsten

> --------------
> Murilo Perrone
> CertiSign
> 
> _______________________________________________
> Muscle mailing list
> [email protected]
> http://lists.drizzle.com/mailman/listinfo/muscle


_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to