Global Platform library underlying GPShell builds easily on Win32, using Visual Studio 2005.
Using cygwin shell 1. tar -xvf the distribution 2. unix2dos the visual studio .sln and .vcproj files Using a Windows Shell 3. download win32 openssl into c:\OpenSSL 4. download and unzip zlib into c:\ 5. copy zlib dll to c:\windows\system32 Using Visual Studio IDE 6. Change project settings for library directories to "c:\zlib123-dll\lib";C:\OpenSSL\lib\VC\static 7. Change project settings for include directories to "c:\zlib123-dll\include";c:\OpenSSL\include 8. specify as link dependencies the elements: ssleay32MTd.lib libeay32MTd.lib winscard.lib zdll.lib 9. Change c++ compile settings to /MTd. 10. Remove post build action 11. Rebuild all GPShell builds just as easily on Win32, using Visual Studio 2005. Using cygwin shell 1. tar -xvf the distribution 2. unix2dos the visual studio .sln and .vcproj files Obviously, reference your own GP library to tailor your own GP offline client to your requirements >From early trials with the default GPShell distribution, command line >parameters in "put key" are missing the ability to specify how they APDU >should vary its key index and the algorithm byte (per 16bit DES3 key). >Building and using the src library should allow one to now specify alternative >defaults for putkey (e.g. 0x81 for the algorithm byte). Having bound to a well-administered musclecard and verified a users pin, one should be reasonably safe in establishing a secure channel to enabled applets or security domains, citing unique enc and mac keys per card. having access the CPLC and performed muscle pin verification, the card is reasonably well identified. This procedures will mitigate the risk of card blocking, due to failed GP handshakes.
_______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
