133944 - google search attempts to write to installation tree

Status: RESOLVED EXPIRED

(SeaMonkey :: Search, defect)

Description

[Colin Blake]

When doing a Google search, Mozilla attempts to open the following file for 
write access:

  searchplugins/google.src

Mozilla shouldn't be trying to write to the installation tree AT ALL. In a 
multi-user environment, normal users will only have read access to files in the 
mozilla installation tree.

Note that the google search still works (I believe), so mozilla must "back off" 
and open the file read only(?), but the failed open operation causes a security 
alarm on OpenVMS and this is most undesirable.

Comment 1

[Samir Gehani]

This may be occuring in two situations:
(a) we wrongly want read-write access when reading the sherlock plugins to 
    parse search results
(b) we need write access when updating the sherlock plugins

Moving to mozilla1.2 although it would be great if someone could contribute a
patch for this sooner.

Comment 2

[julius ross]

this is related to  bug 123315

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420