Jim wrote:
humptydumpty wrote:
Jim wrote:
I just installed this release. During the install, I received a Norton
Antivirus alert that Suspicious.Cloud.7.F was detected and it "fixed it"
(like fixing a cat maybe :) ).
Anyway, according to MozillaZine, it says this is a false positive,
associated with Foxfire and Sea Monkey. So what did Norton "screw up"
by dealing with this "problem"?
The identical issue happened to me. The Norton fix was to remove the
file which further research identified as nssckbi.dll. In my case, the
result was a certificate error at every secure site I attempted to visit
from my bookmarks.
I did a system restore and am back to running SM 2.12.1 with no problems.
By golly Mr. Dumpty, I believe you are correct. I also get a security
error at every secure site I visit. As an aside, I first noticed this
when I did a Google search. I never knew that Google had a secure site
until now, but that's where Sea Monkey sent me. For now, I am just
checking out the certificates and then accepting them if the web site is
a legitimate one I go to, and the certificate appears to jive.
All --
I followed up with Norton with this problem on their forums. The fix
that worked for me -- they told me to restored the file from quarantine
and Norton would no longer mess with it. I did that and that worked.
Also, I submitted the .dll to Norton, and they said they couldn't
reproduce the problem. From the forum users, it appears that some PCs
had the problem and some didn't -- but not sure if they all had this
release of SeaMonkey and Norton.
Also, Norton may have fixed the problem in their antivirus prior to my
file submission.
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
