dinkmeister wrote:
you could always write a small hack to the part that loads the dll and
have it search for that specific dll and take off the path ;)

Yes, and if you did that, you would prevent any smartcard PKCS#11 library from ever working with Mozilla in the future, since they would get loaded from the wrong path also. The absolute reference is necessary because secmod.db contains references to third party DLLs, ie. cryptographic plug-ins, except that unlike browser plug-ins, those don't necessary live inside the Mozilla tree.




On Sun, 18 Apr 2004 22:39:04 -0500, Michael Kaply wrote:

:William L. Hartzell wrote:
:> :> What effect does using LIBPATHSTRICT=1 have upon this issue? Would not :> in this case each version would load its own version of the dll?
:
:No, because the security code hardcodes a fully qualified path to the DLL.
:
:Mike

_______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto

Reply via email to