$Bill wrote:
This are the messages I get when tryin to go to a secure site :

"You cannot connect to x.y.z because SSL is disabled"
"Could not initialize the browser's security component.  The most likely cause
is problems with files in your browser's profile directory. [...]"

There is over 100MB of free space on the profile directory drive.

It's really nice of them not to tell you which file might be the
culprit here.
[...]
I probably should have tried them one at a time, but maybe the next guy
can figure it out.

Inside your profile there is a file secmod.db.

It points to an element inside the GRE part of mozilla, that is stored inside the "common File". That might be the culprit if none of the file inside the profile directory seems to be impacted.

Open the secmod.db binary file, and serahc for the string "Builtin Roots Module", the path is just after that.
_______________________________________________
Mozilla-security mailing list
[EMAIL PROTECTED]
http://mail.mozilla.org/listinfo/mozilla-security

Reply via email to