271101 - FSECURE parental control asks for password when Firefox is started

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Wulf Luck]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I run F-Secure Internet Security 20005 with activated parental control
(Kindersicherung). When I start Mozilla Firefox 1.0 (Firefox is set to the homepage 
www.google.com), Fsecure request the password for the parental control.
Therefore it does not make sense to activate the F-secure parental control with
Firefox. A real pity, since I really like Firefox and would like to ask the
other users of the PC to use it as well. Is this problem known? Is taken care of
by someone? Should I try to solve it?

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Hermann Schwab]

Maybe you can configure FSECURE to allow Firefox to access the Internet.
Maybe you can configure the Passwordmanager of Firefox to give the Password
automatically.
If I understand you correctly, that will not be an option, because the same
password would be given if your child does a search for pr0n.
How does Fsecure react to other browsers starting, let´s say IE, Opera,
Netscape4 if you still got one?
There is a difference between Firefox/Mozilla and the other browsers mentionend
above. Mozilla has a security module, which communicates with mozilla over
sockets. When I´m starting Mozilla, or Firefox, my Firewall ( some older
ZoneAlarm) ask me wether I will allow Firefox/Mozilla to act as a server, that´s
surprising. A browser is a browser, not a server.
Using sockets demands that you allow mozilla acting as a server, locally.
You don´t have to allow it acting as a server to the internet, also the sockets
are used locally only. Maybe that difference triggers FSECURE.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.