Norton Internet Security (Personal Firewall) doesn't recognize Mozilla

RESOLVED FIXED in Jul

Status

Tech Evangelism Graveyard
English US
P1
normal
RESOLVED FIXED
17 years ago
3 years ago

People

(Reporter: Patrick, Assigned: Patrick)

Tracking

unspecified
x86
Windows 98

Details

(Whiteboard: [aok])

(Assignee)

Description

17 years ago
Norton Internet Security (Symantec) doesn't recognize Mozilla as a browser. It
is a firewall and has a set of preset rules for known applications. Mozilla is
not in this set as it could be expected: the user has to create the rules
manually which can be confusing for some users and annoying for many.

Comment 1

17 years ago
I can't confirm this, but I think it's safe to assume that this is ok. bc, this 
needs some nscp love.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

17 years ago
reporter, can you give us a url?

Updated

17 years ago
Priority: -- → P1
(Assignee)

Comment 3

17 years ago
What URL do you expect?
(I'm on my way to find a place where you can download a trial version of the
program if it's what you want.)
(Assignee)

Comment 4

17 years ago
You can find it at:
http://www.symantecstore.com/dr/v2/ec_MAIN.Entry10?V1=313545&PN=1&SP=10023&xid=35375
or for a smaller download, the personal firewall should do it:
http://www.symantecstore.com/dr/v2/ec_MAIN.Entry10?V1=313546&PN=1&SP=10023&xid=35375

Anything else?

Comment 5

17 years ago
thanks
(Assignee)

Comment 6

17 years ago
To clarify things:

This firewall has two features that when badly combined give an annoying result:
  - a set of predefined rules,
  - an ability to recognise when a programme accessing the 'net has been
modified (e.g. updated) ~ fingerpirnt.

Mozilla is not in the set of predifined rules and its fingerprint changes very
often: creating a set of rules each time you update Mozilla is real pain as
there is no way to update the fingerprint in the firewall.

For what evangelism is concerned, Mozilla should be added in the set of rules. I
would also be tempted to add that Symantec (in case they read this) should
absolutely add the possibility to update the fingerprint.

Maybe, to speed up things, we should give Symantec all the communications
(protocol, port (local+remote), address, ...) Mozilla is using in normal conditions.

Comment 7

17 years ago
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
(Assignee)

Comment 8

17 years ago
Any news? (Thanks!)
(Assignee)

Comment 9

17 years ago
A new set of rules was just released but still no Mozilla in it. Any news on
your side?

Comment 10

17 years ago
contacted via
http://service2.symantec.com/discuss/support/feedback2.nsf/product+feedback
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.7
(Assignee)

Comment 11

16 years ago
A new set of rules released today. Mozilla still unknown.

Updated

16 years ago
Whiteboard: [aok]

Comment 12

16 years ago
http://service1.symantec.com/SUPPORT/nav.nsf/396b6ccde72d4a4d882569fc006071d4/bba4642a777392bb88256952006738b3?OpenDocument

-> wontfix 
sorry
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → WONTFIX
(Assignee)

Comment 13

16 years ago
Bob,

We have a misunderstanding here. The link you gave talks about Norton Antivirus.
I was talking about the firewall part of NIS. Reopening. Sorry too.

I've tried my part of evangelism but without much success. I hope that your
@netscape.com will help. For them, it's very easy to fix: it's just a few lines
of configuration.

Please ask me for more info if needed!

Patrick
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---

Comment 14

16 years ago
I have written them to no effect.
Assignee: bclary → Patrick.Smart
Status: REOPENED → NEW
(Assignee)

Comment 15

16 years ago
Taking (at least trying...).

Bob,
Could you please mail me what you sent to give me some inspiration? Thanks!

Patrick
Status: NEW → ASSIGNED
Summary: Norton Internet Security doesn't recognize Mozilla → Norton Internet Security (Personal Firewall) doesn't recognize Mozilla
Target Milestone: Dec → Apr
(Assignee)

Comment 16

16 years ago
Sorry for the lack of updates but I had no test platform for a while. Since the
problem is still not solved, please find my note to them and their reply:

---

>>Mozilla 1.0 is now released. Could you please add a predefined
>>auto-config rule for it in your definitions for NIS?

Thanks for letting us know. I will pass this onto our developers/

Please let us know if we can provide more assistance to you.


Regards,

Donald Hess
Symantec Technical Support

---

Marking to be solved in June as a reminder.
Target Milestone: Apr → Jun
(Assignee)

Comment 17

16 years ago
Since no move has been seen I posted to
http://service4.symantec.com/discuss/support/feedback2.nsf/product+feedback :

---
Suggestion: add Mozilla to predefined firewall rules.
Fact: this has been suggested more than one month ago (and many oher times
before) but has not been done.
Question: is it that much of work to add a new rule or is Mozilla such a low
priority for you?
URL: http://bugzilla.mozilla.org/show_bug.cgi?id=78454

Thank you in advance!

Patrick
---
Target Milestone: Jun → Jul

Comment 18

15 years ago
This works since late 2002 - Norton Personal Firewall automatically creates web
access rules for Mozilla. Now, it's Phoenix’s turn to be recognized, but that
should be a different bug. I propose to mark this bug FIXED.

Tested: NPF 2003 with Mozilla1.3b.

Comment 19

15 years ago
Patrick, can you confirm this is fixed and mark so?
(Assignee)

Comment 20

15 years ago
Sorry for the delay: I was "out of business" for a while.
It's fixed indeed.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago15 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.