On Sun, 2011-01-30 at 16:26 +0100, Diego Elio Pettenò wrote: > Il giorno mer, 26/01/2011 alle 14.21 -0600, Kent Yoder ha scritto: > > The loop in there goes through the .so locations it > > pulls out of /var/lib/opencryptoki/pk_config_data for each token and > > tries to dlopen them. We let the runtime linker figure out whether it > > should be doing the 32 or 64bit version. > > Okay this all looks great then. On the other hand, libopencryptoki (the > api) should be linked against and not dlopened by default, which means > _that_ one should be in the linkers search paths (both link editor and > runtime loader), and right now it isn't.
For some time we've been using an opencryptoki specific conf file in /etc/ld.so.conf.d to accomplish this, so it should be in the linker path... > Also, how much code are we talking about to rely on the "old" names? At > least in Gentoo there is no software using opencryptoki so our interest > in keeping old compatibility symlinks is pretty much none. Understandable. There is no code that's required to process those .so's, its simply a redirect to the real library for old apps that hard-coded /usr/lib/pkcs11/PKCS11_API.so. > At any rate at a minimum even if not changing the name, -module should > be used; refer to this documentation of mine for as to why: > > http://www.flameeyes.eu/autotools-mythbuster/libtool/plugins.html > I'm not sure this applies since there is no library without the lib prefix, just a soft link... Kent ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Opencryptoki-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
