Closed Bug 806260 Opened 12 years ago Closed 12 years ago

Norton did not dig your download site. Referenced Cloud.7.F as Suspicious & quarantined nssckbi.dll.

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Version:
SeaMonkey 2.13 Branch
Platform:
x86_64
Windows 7
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: degodave, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Firefox/16.0 SeaMonkey/2.13.2
Build ID: 20121026204328

Steps to reproduce:

Disabled Norton 360 auto protect and installed SeaMonkey direct from the site then turned Norton back on. 


Actual results:

Seems to have been an effective work around but will I have to do this every time now? SeaMonkey is running fine now.


Expected results:

Update my old version of SeaMonkey just as I have been doing for years with no hangups or static from Norton.
This sounds more like a Norton bug than a Mozilla bug to me.

Is there a way to report bugs to Norton, and if there is, did you use it? What was the result (if any)?
Flags: needinfo?(degodave)
Callek has submitted 2.13.2 to Norton for whitelisting. Unfortunately it was submitted on Saturday (weekend). No news from them yet. Probably Sandy is occupying their attention at the moment.
Flags: needinfo?(degodave)
Depends on: SM2.13.2
This should be fixed now. Norton has added SM 2.13.2 to their whitelist. Please check and let us know.
Flags: needinfo?(degodave)
Whiteboard: [CLOSEME 2012-11-10 WFM]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Flags: needinfo?(degodave)
Resolution: --- → WORKSFORME
Whiteboard: [CLOSEME 2012-11-10 WFM]
You need to log in before you can comment on or make changes to this bug.