diff options
author | kinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-01 11:52:31 +0000 |
---|---|---|
committer | kinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-07-01 11:52:31 +0000 |
commit | ce5cbed872693ef89bb6e33fa4dd513b1dd7054b (patch) | |
tree | aae7f224608f012d54cdb7141c4d8bfd8ad0b3e6 /content/content_shell.gypi | |
parent | 5e5ba0428effebbcce06382c792f5c9d2afc1ab8 (diff) | |
download | chromium_src-ce5cbed872693ef89bb6e33fa4dd513b1dd7054b.zip chromium_src-ce5cbed872693ef89bb6e33fa4dd513b1dd7054b.tar.gz chromium_src-ce5cbed872693ef89bb6e33fa4dd513b1dd7054b.tar.bz2 |
Implement ChildProcessSecurityPolicy::HasPermissionsForFileSystemFile()
In content/ layer:
- Add CPSP::HasPermissionsForFileSystemFile() for central
FileSystem permission check.
- Replace all permission check code for FileSystem files with the
newly added CPSP method
In webkit/browser/fileapi layer:
- Each MountPointProvider's GetPermissionPolicy() is replaced with a
central static FileSystemContext::GetPermissionPolicy() method.
Now the permission policy is statically defined for each type and
used by CPSP. Some FS-specific security checks are moved into
each FS's private implementation.
- For SandboxMountPointProvider: moved some API-specific validity
check code into a private IsAcessValid() method.
- For CrosMountPointProvider: IsAccessAllowed() method is still called
every time when a new FileSystemOperation is created, but doesn't
participate the CPSP's permission check.
BUG=174550
TEST=ChildProcessSecurityPolicyTest::FileSystemFilePermissions
R=aedla@chromium.org, darin@chromium.org, tbarzic@chromium.org, tsepez@chromium.org
Review URL: https://codereview.chromium.org/12310099
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@209418 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/content_shell.gypi')
0 files changed, 0 insertions, 0 deletions