Re: [opensc-devel] OpenSC 0.12.1 RC1
2011/5/12 Johannes Becker johannes.bec...@hrz.uni-giessen.de Am Freitag 29 April 2011 schrieb Martin Paljak: I froze r5409 [1] as OpenSC 0.12.1 RC1. It works with iceweasel (firefox) and CardOS V4.3B It doesn't work with TCOS 2 . This the same with OpenSC 0.12.0, we discussed the problem without a solution last september and probably tracked it down to the missing token flag: login required shown then by pkcs11-tool -L Johannes, could you please test with version 5508. TCOS2 should work again. Now the command pkcs11-tool in OpenSC 0.12.1 RC1 doesn't work at all. You get $ pkcs11-tool -L error: Failed to load pkcs11 module Aborting. I don't think this problem (pkcs11-tool cannot load module) has anything to do with the above TCOS2-problem. Does this problem happen with TCOS-cards only? Maybe specifying the module path will helo, i.e. pkcs11-tool --module /path/to/opensc-pkcs11.so -L Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] OpenSC now supports TCOS3 IdKey cards
Hi I just added support for IDKey cards ( http://www.telesec.de/tcos/LB_IDKey_100318_dt.pdf ). If anybody out there is using this card with OpenSC (besides me) please let me know wether it works or not. Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] Static link for opensc-pkcs11.dll
Hello, I would like to link statically the PKCS#11 module for Windows, or at least to include the static version of this module into the MSI . Here in attachment there in the diff for the build procedure (it presumes the change of link mode for the actual PKCS#11 module dll). Have you any objections, please? Kind wishes, Viktor. Index: src/libopensc/Makefile.mak === --- src/libopensc/Makefile.mak (révision 5507) +++ src/libopensc/Makefile.mak (copie de travail) @@ -44,4 +44,4 @@ if EXIST opensc.dll.manifest mt -manifest opensc.dll.manifest -outputresource:opensc.dll;2 opensc_a.lib: $(OBJECTS) ..\scconf\scconf.lib ..\common\common.lib ..\pkcs15init\pkcs15init.lib - lib $(LIBFLAGS) /out:opensc_a.lib $(OBJECTS) ..\scconf\scconf.lib ..\common\common.lib ..\pkcs15init\pkcs15init.lib user32.lib + lib $(LIBFLAGS) /out:opensc_a.lib $(OBJECTS) ..\scconf\scconf.lib ..\common\common.lib ..\common\libscdl.lib ..\pkcs15init\pkcs15init.lib $(ZLIB_LIB) user32.lib ws2_32.lib Index: src/pkcs11/Makefile.mak === --- src/pkcs11/Makefile.mak (révision 5507) +++ src/pkcs11/Makefile.mak (copie de travail) @@ -22,11 +22,11 @@ link $(LINKFLAGS) /dll /def:$*.def /implib:$*.lib /out:$(TARGET0) $(OBJECTS) hack-enabled.obj ..\libopensc\opensc.lib ..\scconf\scconf.lib ..\pkcs15init\pkcs15init.lib ..\common\common.lib $(OPENSSL_LIB) gdi32.lib if EXIST $(TARGET0).manifest mt -manifest $(TARGET0).manifest -outputresource:$(TARGET0);2 -$(TARGET): $(OBJECTS) hack-disabled.obj ..\libopensc\opensc.lib ..\scconf\scconf.lib ..\pkcs15init\pkcs15init.lib ..\common\common.lib +$(TARGET): $(OBJECTS) hack-disabled.obj ..\libopensc\opensc_a.lib ..\pkcs15init\pkcs15init.lib echo LIBRARY $* $*.def echo EXPORTS $*.def type $*.exports $*.def - link $(LINKFLAGS) /dll /def:$*.def /implib:$*.lib /out:$(TARGET) $(OBJECTS) hack-disabled.obj ..\libopensc\opensc.lib ..\scconf\scconf.lib ..\pkcs15init\pkcs15init.lib ..\common\common.lib $(OPENSSL_LIB) gdi32.lib + link $(LINKFLAGS) /dll /def:$*.def /implib:$*.lib /out:$(TARGET) $(OBJECTS) hack-disabled.obj ..\libopensc\opensc_a.lib ..\pkcs15init\pkcs15init.lib $(OPENSSL_LIB) gdi32.lib if EXIST $(TARGET).manifest mt -manifest $(TARGET).manifest -outputresource:$(TARGET);2 $(TARGET3): $(OBJECTS3) ..\libopensc\opensc.lib ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] Static link for opensc-pkcs11.dll
This is only for MSC build, not for mingw. But as this project is going to MSC release anyway... On Sat, May 28, 2011 at 11:07 PM, Viktor Tarasov viktor.tara...@gmail.com wrote: Hello, I would like to link statically the PKCS#11 module for Windows, or at least to include the static version of this module into the MSI . Here in attachment there in the diff for the build procedure (it presumes the change of link mode for the actual PKCS#11 module dll). Have you any objections, please? Kind wishes, Viktor. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] Static link for opensc-pkcs11.dll
Hello, On May 28, 2011, at 22:07 , Viktor Tarasov wrote: I would like to link statically the PKCS#11 module for Windows, or at least to include the static version of this module into the MSI . Why? -- @MartinPaljak.net +3725156495 ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] Static link for opensc-pkcs11.dll
Le 28/05/2011 22:26, Martin Paljak a écrit : Hello, On May 28, 2011, at 22:07 , Viktor Tarasov wrote: I would like to link statically the PKCS#11 module for Windows, or at least to include the static version of this module into the MSI . Why? It's a question of using of the different versions of opensc on the same platform. I have a xulrunner application that uses the old modified version of opensc.dll and that needs to be used with the actual OpenSC PKCS#11 module . Static linking will allow the peaceful cohabitation. Kind regards, Viktor. ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
