[opensc-devel] DLL installation in SCB.
Hi, I installed SCB-0.7 from the homepage and updated the contained opensc library to the current SVN by compiling opensc on my own using VC++ 8. Everything went fine, until I tried to use opensc-pkcs11.dll from within JAVA, which did not work. After several hours banging my head against a wall, I recognized, that JAVA was loading the old version of opensc.dll, which has been installed by the SCB installer to C:\WINDOWS\System32 After deleting the opensc-dlls from C:\WINDOWS\System32, everything went smooth, openssl and JAVA now use the new opensc version flawlessly. So I have the following remarks/questions to the SCB installation: 1) Are there any good reasons to install the opensc dlls twice? (SCB install directory and C:\WINDOWS\System32) Installing then only in the SCB install directory should be IMHO sufficient, because all dlls on which the opensc libs depeand are installed alongside in the same directory, so they are resolved anyways. 2) The MSVC 7.1 compiler used to compile the binary distribution of SCB creates dependencies on msvcr71.dll, which is *not* layer atop the more frequently used msvcrt.dll originating from msvc6. msvcrt.dll shipped together with Win2K/WinXP and used by a bunch of libraries out there. Therefore, it would be more feasible to use either mingw (is this fully supported by now?) or at least msvc8 to build the binary SCB distribution. The build notes on the opensc WIKI lead the user to the Visual Studio express download, which contains msvc8. The msvc8 CRT library, msvcr80.dll corrects the redundant installation of multiple CRT dlls, by *extending* the functionality of msvcrt.dll instead of replacing it. Best regards, Wolfgang ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] DLL installation in SCB.
On Sat, Aug 12, 2006 at 10:35:49AM +0200, Wolfgang Glas wrote: > Therefore, it would be more feasible to use either mingw (is this > fully supported by now?) I also think this is a good idea. I would have made some experiments but haven't found the time.. Please feel free to try it out. If it works with MinGW then perhaps it can be made to work also when cross-compiling and voila there's automated builds.. //Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] new versions: pcsc-lite 1.3.2, ccid 1.1.0, pcsc-perl 1.4.4, pcsc-tools 1.4.6
Hello, pcsc-lite [1] and my CCID driver [2] now support extended APDU out of the box. You can send and receive up to 64KB of data if your card (and reader) supports it. The extended APDUs are supported only for T=1 cards and if the reader is in TPDU mode or extended APDU mode (not in character mode or short APDU mode). I also upgraded pcsc-perl [3] and pcsc-tools [4] to benefit from this new feature. Enjoy! Changelogs: * pcsc-lite pcsc-lite-1.3.2: Ludovic Rousseau 11 August 2006 - add support of extended APDU in the standard configuration and in a backward compatible way: pcscd 1.3.2 can be used with libpcsclite <= 1.3.2 - define MAX_BUFFER_SIZE_EXTENDED as the maximal size allowed for a extended APDU (64KB) - LPCTSTR and LPTSTR types are deprecated. Use LPCSTR and LPSTR instead - Dual licence src/error.c so it can be used bu OpenSC. It is now BSD-like, see the COPYING file and GNU Lesser General Licence 2.1 or (at your option) any later version - document that the 4 bytes field value in PCSC_TLV_STRUCTURE is always in big endian as documented in PCSC v2 part 10 ch 2.2 page 2. You can use ntohl() to convert the value. Thanks to Ulrich Vogl for the bug report - some other minor improvements and bug corrections * ccid 1.1.0 - 11 August 2006, Ludovic Rousseau - support Extended APDU (up to 64KB) for readers in TPDU mode (many readers) or Extended APDU mode (very rare). This only works for T=1 cards. - add support for C3PO LTC31 (new version), OmniKey CardMan 3021, HP USB Smart Card Keyboard, Actividentity (ActiveCard) Activkey Sim, id3 Semiconductors CL1356D and CL1356T, Alcor Micro AU9520 - support the contactless interface of the SCR331-DI-NTTCOM - add support of FreeBSD - increase the USB timeout used for PIN verify/modify to not timeout before the reader - the 4-bytes value returned by CM_IOCTL_GET_FEATURE_REQUEST shall be encoded in big endian as documented in PCSC v2 part 10 ch 2.2 page 2. The applications using this feature shall be updated (to respect the PCSC specification). - use ./configure --enable-twinserial to compile and install the the driver for the GemPC Twin serial - some minor bugs removed * pcsc-perl 1.4.4 - 12 August 2006, Ludovic ROUSSEAU - add support of extended APDU * pcsc-tools 1.4.6 - 12 August 2006, Ludovic ROUSSEAU - 28 new ATRs in smartcard_list.txt - scriptor/gscriptor: allow multi-lines input and wrap long output. lines ending with \ are to continue on the next line. More easy to use a 64K-bytes long APDU. [1] https://alioth.debian.org/project/showfiles.php?group_id=30105 [2] http://pcsclite.alioth.debian.org/ccid.html [3] http://ludovic.rousseau.free.fr/softwares/pcsc-perl/ [4] http://ludovic.rousseau.free.fr/softwares/pcsc-tools/ -- Dr. Ludovic Rousseau ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
