The default bug view has changed. See this FAQ.

greprefs subdirectory; modes too much restrictive

RESOLVED INVALID

Status

SeaMonkey
Build Config
RESOLVED INVALID
13 years ago
9 years ago

People

(Reporter: Jehan Procaccia, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922

When installaling mozilla-1.7.3 from Red Hat RPM on a fedora Core 2 system,
/usr/lib/mozilla-1.7.3/greprefs get modes 700 which only allow root to launch
mozilla while using autoconfiguration of mozilla. Other unprevileged user cannot
read that directory , and mozilla freeze on an unterminable futex and a
gettimeofday ...

indeed for unprivilegde user I get from strace :
open("/usr/lib/mozilla-1.7.3/greprefs",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 EACCES (Permission denied)
open("/usr/lib/mozilla-1.7.3/defaults/pref",
O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
...


Reproducible: Always
Steps to Reproduce:
1. check that mode a 700 on greprefs directory
2. start mozilla as non root
3. 

Actual Results:  
it freeze

Expected Results:  
it start !

If I set /usr/lib/mozilla-1.7.3/greprefs modes 755 then everything is fine !
Why modes a so restrictive on greprefs directory ? is it dangerous to set it to
755 ? is it a bug, or a wrong packaging from the RPM ?
bsmedberg, is this a problem of make install, or is redhat to blame? :-)
http://lxr.mozilla.org/mozilla/source/config/rules.mk#1233

We use nsinstall -D, I suppose there must be flags to change the security for
the created dir but I don't know what they are.
Assignee: prefs → nobody
Status: UNCONFIRMED → NEW
Component: Preferences → Build Config
Ever confirmed: true
QA Contact: core.build-config
Product: Browser → Seamonkey
Currently, the only SeaMonkey-trunk Linux-i686 distributions are in .tar.gz (without installer) and .complete.mar format. Other packagings (such as RPM) are the responsibility of redistributors (such as RedHat etc.) and ought not to use trunk builds anyway.

=> INVALID.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.