Ladies and Gentlemen,
I am trying to build coolkey-1.1.0 on FreeBSD 7.0-beta2.
After extracting the coolkey source tarball, I built coolkey with the following steps:
vi configure
:%s/-ldl/-lc/g
(This step was necessary because unlike Linux, FreeBSD's libc contains the functionality found in libdl on Linux, so there is no libdl on FreeBSD. I'm sure there's a more elegant way to accomplish this but this is how I did it).
env CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib PCSC_CFLAGS=-I/usr/local/include/PCSC PCSC_LIBS=-L/usr/local/lib NSS_CFLAGS=-I/usr/local/include/nss/nss NSS_LIBS=-L/usr/local/lib/nss ./configure --prefix=/usr/opt
gmake
gmake install
I should note that PCSC (installed through Ports) is apparently functioning properly and that the light on my SCM 331 smart card reader blinks when I insert my CAC. I successfully built commonAccessCard.bundle using Apple's CACPlugin and the muscle framework and using that am able to view the certificates on my CAC, so the problem does not seem to lie with my hardware or PCSC. Unfortunately, commonAccessCard.bundle has its share of problems and after choosing a certificate and entering my PIN at AF Portal or other secure DoD sites, I receive an NSS error. (Error code -12222). Inquiries on the MUSCLE mailing list led to the conclusion that commonAccessCard.bundle is unstable and coolkey the better solution for CAC access on Mozilla products.
When I try to add libcoolkeypk11.so as a Security Module in Firefox, the dinosaur segfaults without an error message. (Exit code 139).
An ldd of libcoolkeypk11.so reveals:
/usr/opt/lib/pkcs11/libcoolkeypk11.so:
libckyapplet.so.1 => /usr/opt/lib/libckyapplet.so.1 (0x281a6000)
libz.so.4 => /lib/libz.so.4 (0x281b1000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x28300000)
libm.so.5 => /lib/libm.so.5 (0x281c3000)
libc.so.7 => /lib/libc.so.7 (0x28089000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x281d8000)
An ldd of libckyapplet.so.1 reveals:
/usr/opt/lib/libckyapplet.so.1:
libz.so.4 => /lib/libz.so.4 (0x28190000)
libc.so.7 => /lib/libc.so.7 (0x28089000)
Should either of these coolkey shared objects be explicitly linked to libpcsclite.so.1?
coolkey's src/install/Makefile reveals that it correctly recognizes SCARD_LIB_NAME = libpcsclite.so.1 which it is looking for in PCSC_LIBS = -L/usr/local/lib.
Has anyone successfully tested coolkey on a *BSD system? Building it on FreeBSD is easy enough. Loading it as a security module in Firefox is not.
V/r,
Kevin Reinholz
_______________________________________________
Coolkey-devel mailing list
Coolkey-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/coolkey-devel
