Closed Bug 761438 Opened 12 years ago Closed 12 years ago

B2G filesystem permissions

Categories

(Firefox OS Graveyard :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(blocking-basecamp:+)

RESOLVED FIXED
blocking-basecamp +

People

(Reporter: kang, Assigned: kang)

References

Details

(Whiteboard: [WebAPI:P0][LOE:S])

Hopefully this is the right component (and not github) for this one bug.

It seems gecko is creating a few directories with a wide open umask, unless those are chmoded for any reason (resulting in 0777 or 0666 file/dirs)

List:

/data/b2g/mozilla/2n2g4pgx.default/.parentlock
/data/b2g/mozilla/2n2g4pgx.default/startupCache
/data/b2g/mozilla/2n2g4pgx.default/localstore.rdf
/data/b2g/mozilla/profiles.ini
/cache/Cache

The last one is the most important but ideally all of them should be created with a sensible umask (at least, 022 which results into 0644 files, or rw-r--r--), or if they do need 777 for directories, with the sticky t bit set (restricted deletion, i.e. like /tmp).

If those files are created elsewhere, and belong to another component, I couldn't find it, but please let me know :)
We need to fix our umask, or buggy content processes will be able to hose files on the fs that they shouldn't be able to see at all.
blocking-basecamp: --- → ?
Assignee: nobody → gdestuynder
Whiteboard: [WebAPI:P0]
Whiteboard: [WebAPI:P0] → [WebAPI:P0][LOE:S]
See https://github.com/mozilla-b2g/gonk-misc/pull/27

note that this does not fix pushing stuff via adb during gaia install if adb has umask 000
gaia should probably be written as an image instead
pull request has been accepted
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.