Security/Sandbox/Deny Filesystem Access: Difference between revisions

Line 42: Line 42:
Web content can use chrome:// and resource:// URI's.
Web content can use chrome:// and resource:// URI's.


Another approach is to allow read access to the place within the profile that addons/Firefox store chrome:// and resource:// files. billm suspects those are safe locations that don't contain sensitive data.
Another approach is to give the content process read access to the these chrome:// and resource:// files. That would be a place in the profile and also the Firefox install bundle. billm suspects those are safe locations in the profile that don't contain sensitive data.
|-
|-
| {{bug|1109293}} Desktop content process resource:// and moz-extension:// URIs should not directly use file:/// || Might block how we handle file:// URI's ||  
| {{bug|1109293}} Desktop content process resource:// and moz-extension:// URIs should not directly use file:/// || Might block how we handle file:// URI's ||  
202

edits