Mike,
Michael Kaply wrote:
Julien Pierre wrote:
> 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.
No, you are missing the point. Applications A and B (in this case different releases of Mozilla, where B is newer than A) were not designed to share a profile back & forth.
Only migrating from A to B is officially supported. Migrating from B to A is not, and there are many other reasons than security why this is the case.
You should focus on making the A to B case work. The B to A case is invalid and unsupported.
The A to B case does work if you install the new version OVER the old version, which is the "expected" behavior.
I can't believe that you would argue that hardcoding a path to a DLL in a profile is somehow correct behavior.
The point is moot. It can't be fixed anymore without breaking lots of stuff. what's done is done.
Mike
_______________________________________________ mozilla-crypto mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-crypto
