Closed
Bug 309302
Opened 19 years ago
Closed 17 years ago
Inconsistent naming of NT registry entries (e.g. some in HKEY_CURRENT_USER\Netscape\Netscape_Navigator)
Categories
(Firefox :: Security, enhancement)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bugzilla-support, Unassigned)
Details
(Whiteboard: CLOSEME 08/07, DUPEME?)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050908 Firefox/1.4 During installation, it appears that a default set of MIME types appear in the registry under the key "HKEY_CURRENT_USER\Netscape\Netscape_Navigator". I don't remember installing "Netscape Navigator", however, I do remember installing "Firefox". Why are these keys here? To have keys created in areas of the registry not visually connected with an application I have installed is a breeding ground for security-hole exploiters. Why can't everything just be filed under the "Mozilla...Firefox" keys? Reproducible: Always Steps to Reproduce: 1. Install Firefox Expected Results: All keys should be filed under a single point and consistently named. Automatic registry sweepers checking for potentially dubious entries could flag this is sabotage (overwriting what looks like another applications workspace).
Updated•19 years ago
|
Summary: Inconsistent naming of NT registry entries gives scope for hijacking → Inconsistent naming of NT registry entries (e.g. some in HKEY_CURRENT_USER\Netscape\Netscape_Navigator)
Comment 1•17 years ago
|
||
Can you reproduce the problem with the latest Firefox 2 or 3 builds? If not, please close the bug as WORKSFORME. Thanks.
Whiteboard: CLOSEME 08/07, DUPEME?
Comment 2•17 years ago
|
||
http://lxr.mozilla.org/seamonkey/search?string=netscape shows that we are not adding any netscape entries on the trunk which is the only place this would change.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•