1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
|
// Copyright (c) 2012 The Chromium Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
#ifndef CONTENT_PUBLIC_BROWSER_CHILD_PROCESS_SECURITY_POLICY_H_
#define CONTENT_PUBLIC_BROWSER_CHILD_PROCESS_SECURITY_POLICY_H_
#include <set>
#include <string>
#include "base/basictypes.h"
#include "content/common/content_export.h"
class FilePath;
namespace content {
// The ChildProcessSecurityPolicy class is used to grant and revoke security
// capabilities for child processes. For example, it restricts whether a child
// process is permitted to load file:// URLs based on whether the process
// has ever been commanded to load file:// URLs by the browser.
//
// ChildProcessSecurityPolicy is a singleton that may be used on any thread.
//
class ChildProcessSecurityPolicy {
public:
virtual ~ChildProcessSecurityPolicy() {}
// There is one global ChildProcessSecurityPolicy object for the entire
// browser process. The object returned by this method may be accessed on
// any thread.
static CONTENT_EXPORT ChildProcessSecurityPolicy* GetInstance();
// Web-safe schemes can be requested by any child process. Once a web-safe
// scheme has been registered, any child process can request URLs with
// that scheme. There is no mechanism for revoking web-safe schemes.
virtual void RegisterWebSafeScheme(const std::string& scheme) = 0;
// Returns true iff |scheme| has been registered as a web-safe scheme.
virtual bool IsWebSafeScheme(const std::string& scheme) = 0;
// Sets the list of disabled schemes.
// URLs using these schemes won't be loaded at all. The previous list of
// schemes is overwritten. An empty |schemes| disables this feature.
// Schemes listed as disabled take precedence over Web-safe schemes.
virtual void RegisterDisabledSchemes(
const std::set<std::string>& schemes) = 0;
// Grants certain permissions to a file. |permissions| must be a bit-set of
// base::PlatformFileFlags.
virtual void GrantPermissionsForFile(int child_id,
const FilePath& file,
int permissions) = 0;
// Before servicing a child process's request to upload a file to the web, the
// browser should call this method to determine whether the process has the
// capability to upload the requested file.
virtual bool CanReadFile(int child_id, const FilePath& file) = 0;
// Whenever the user picks a file from a <input type="file"> element, the
// browser should call this function to grant the child process the capability
// to upload the file to the web.
virtual void GrantReadFile(int child_id, const FilePath& file) = 0;
// Grants read access permission to the given isolated file system
// identified by |filesystem_id|. An isolated file system can be
// created for a set of native files/directories (like dropped files)
// using fileapi::IsolatedContext. A child process needs to be granted
// permission to the file system to access the files in it using
// file system URL.
//
// Note: to grant read access to the content of files you also need
// to give permission directly to the file paths using GrantReadFile.
// TODO(kinuko): We should unify this file-level and file-system-level
// permission when a file is accessed via a file system.
//
// Note: files/directories in the same file system share the same
// permission as far as they are accessed via the file system, i.e.
// using the file system URL (tip: you can create a new file system
// to give different permission to part of files).
virtual void GrantReadFileSystem(int child_id,
const std::string& filesystem_id) = 0;
// Grants write access permission to the given isolated file system
// identified by |filesystem_id|. See comments for GrantReadFileSystem
// for more details. For writing you do NOT need to give direct permission
// to individual file paths.
//
// This must be called with a great care as this gives write permission
// to all files/directories included in the file system.
virtual void GrantWriteFileSystem(int child_id,
const std::string& filesystem_id) = 0;
// Grant create file permission to the given isolated file system identified
// by |filesystem_id|.
// See comments for GrantReadFileSystem for more details. For creating you
// do NOT need to give direct permission to individual file paths.
//
// This must be called with a great care as this gives create permission
// within all directories included in the file system.
virtual void GrantCreateFileForFileSystem(
int child_id,
const std::string& filesystem_id) = 0;
// Grants the child process the capability to access URLs of the provided
// scheme.
virtual void GrantScheme(int child_id, const std::string& scheme) = 0;
// Returns true iff read access has been granted to the file system with
// |filesystem_id|.
virtual bool CanReadFileSystem(int child_id,
const std::string& filesystem_id) = 0;
// Returns true iff read and write access has been granted to the filesystem
// with |filesystem_id|.
virtual bool CanReadWriteFileSystem(int child_id,
const std::string& filesystem_id) = 0;
};
}; // namespace content
#endif // CONTENT_PUBLIC_BROWSER_CHILD_PROCESS_SECURITY_POLICY_H_
|
