Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Why does Firefox force Norton 360 to create a firewall rule that allows ALL inbound/outbound traffic for all ports, ALL communications?

  • Akukho zimpendulo
  • 3 zinale nkinga
  • 2 views
Peristera
Peristera
more options

OK, I know it's Norton 360, but.... Every time I use Firefox - which I just love; Explorer 9 is an absolute bomb - my auto firewall creates a rule for Firefox that allows outbound (OK) AND INBOUND TRAFFIC (SO NOT OK!) - for ALL COMMUNICATIONS (VERY NOT OK) like TCP, UDP, ICMP, et al to/from ALL PORTS/COMPUTERS - COMPLETELY NOT OK.

I delete the rule and allow only outbound TCP/UDP to Ports 53, 80, 443 and then the next time I launch Firefox, the rule is back.

In defense of Norton, it does not do this for every program/app and did not do this for IE 8 or 9. I do block most ports (incoming) and I definitely do not file share or need to AND I do block some outbound NET BIOS info. But that never bothered most browsers in the past.

Can you just tell me what Firefox needs and I will allow it? It should not be forcing Norton into creating such a dangerous rule as allowing all incoming traffic from all ports, all communications, etc.

Firefox is really an incredibly safe browser - but not that safe! No one is. I'm wireless, Vista Home Premium SP2 32-bit.

OK, I know it's Norton 360, but.... Every time I use Firefox - which I just love; Explorer 9 is an absolute bomb - my auto firewall creates a rule for Firefox that allows outbound (OK) AND INBOUND TRAFFIC (SO NOT OK!) - for ALL COMMUNICATIONS (VERY NOT OK) like TCP, UDP, ICMP, et al to/from ALL PORTS/COMPUTERS - COMPLETELY NOT OK. I delete the rule and allow only outbound TCP/UDP to Ports 53, 80, 443 and then the next time I launch Firefox, the rule is back. In defense of Norton, it does not do this for every program/app and did not do this for IE 8 or 9. I do block most ports (incoming) and I definitely do not file share or need to AND I do block some outbound NET BIOS info. But that never bothered most browsers in the past. Can you just tell me what Firefox needs and I will allow it? It should not be forcing Norton into creating such a dangerous rule as allowing all incoming traffic from all ports, all communications, etc. Firefox is really an incredibly safe browser - but not that safe! No one is. I'm wireless, Vista Home Premium SP2 32-bit.