[3171] in Release_7.7_team
Fwd: Working certificates AFTER profile import!
daemon@ATHENA.MIT.EDU (Bill Cattey)
Fri Mar 8 16:08:34 2002
Message-ID: <MwWGVCxz00010HhFdt@mit.edu>
Date: Fri, 8 Mar 2002 21:08:30 +0000 ()
From: Bill Cattey <wdc@MIT.EDU>
To: release-team@MIT.EDU
---------- Forwarded message begins here ----------
Date: Fri, 8 Mar 2002 21:03:07 +0000 ()
From: Bill Cattey <wdc@MIT.EDU>
To: netscape-release@mit.edu
Subject: Working certificates AFTER profile import!
CC: Boris Zbarsky <bzbarsky@mit.edu>
Perhaps this is not a problem for Netscape 6, but it was GREATLY
bothering me in Mozilla. I suspect it is an issue for both.
Symptom:
You run Mozilla for the first time, import your Netscape profile, and
everything works EXCEPT client certificates. You can examine the
certificates just fine, they look perfectly happy, but when you go some
place like the NECX page for MIT, you get "Unknown SSL error -27777" or
some such.
Previous unpleasant work-around:
Chatting with Oliver Thomas about this, he said that if one created a
wholly new profile with NO state carried over, and imported your
certificates by hand, stuff would work. This is unpleasant because all
the wonderful configurations that WERE working get sacrificed for a
single feature.
New Trivial fix:
With Mozilla SHUT DOWN (because it keeps its own copy of this file
internally and will write it out undoing your changes) edit the file
prefs.js in mozilla configuration directory. (It's right next to
bookmarks.html. Mine is in
/mit/wdc/.mozilla/wdc/ytqx9jsh.slt/prefs.js.) as follows:
Look for the 3 lines beginning:
user_pref("security.default_mail_cert"
user_pref("security.default_personal_cert"
user_pref("security.default_proxy_cert"
Delete them.
Run Mozilla
Be happy.
How we got here:
Old versions of Netscape got very confused if you did NOT explicitly
specify certificate defaults. Mozilla has the exact opposite bug.
TODO: Bill submits bug report to mozilla.org to get this fixed.
Share and enjoy,
-wdc
