> a lot of stuff
You are clearly missing the point.
IF I have two applications, application A and application B that happen to be able to share a profile, and I have a DLL that is named the same but different between app A and app B (like foo.dll), and because app A was started first, it hardcoded the path in the profile to use the foo.dll from app A even though app B had a DLL that was newer/better, then what is broke is the profile information.
I'm not going to screw with calling conventions at this point.
The security code should be fixed to use the DLL That corresponds to the Mozilla profile is being used for - it should NOT be hardcoding a path to a specific DLL.
Mike
_______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
