202
edits
Haftandilian (talk | contribs) (Updating section on per-system and per-user Extensions directory) |
Haftandilian (talk | contribs) (Updated section on profile subdirs -- extensions and weave) |
||
Line 525: | Line 525: | ||
|| | || | ||
See the docs on extensions.autoDisableScopes for more information on these paths. The first path allow access to an Extensions directory that applies to all of a user's profiles. The second is for a system-wide Extensions directory that applies to all users. The setting of extensions.autoDisableScopes controls whether or not these locations are used. | See the docs on extensions.autoDisableScopes for more information on these paths. The first path allow access to an Extensions directory that applies to all of a user's profiles. The second is for a system-wide Extensions directory that applies to all users. The setting of extensions.autoDisableScopes controls whether or not these locations are used. | ||
|- id=aar_lib_profile | |||
| | |||
[[#aar_lib_profile|link]] | |||
<pre style="border:none;"> | |||
"; Profile subdirectories\n" | |||
" (if (not (zero? hasProfileDir)) (allow file-read*\n" | |||
" (profile-subpath \"/extensions\")\n" | |||
" (profile-subpath \"/weave\")))\n" | |||
</pre> | |||
|| | |||
These allow access to the extensions and weave subdirectories within the current profile. Read and write access to the profile director is blocked (in other rules). Bug 1295700 was filed to address removing access to sensitive weave sync data. | |||
|- id=aar_home_lib | |- id=aar_home_lib | ||
| | | |
edits