| commit | 2dd70fcff791aa32b77360c9c8ed413d791e5b47 | |
| author | ben <ben@chromium.org> | |
| Fri, 24 Jul 2015 22:22:09 +0000 (24 15:22 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Fri, 24 Jul 2015 22:23:09 +0000 (24 22:23 +0000) | ||
| tree | 00568483c25b7d81c741dbbf4acc913354981c0d | treesnapshot (tar.gz zip) |
| parent | 610e5de27b9f4bc34c43eb6ee78db1acf49e8ef9 | commitdiff |
Allow trusted brokers to restrict connections for spawned applications to whitelisted applications and interfaces.
Currently, filters are not inherited when a restricted application starts a new application. If I did that immediately there is an opportunity for races if a restricted app starts a trusted app before the trusted broker can. I need to think through that in more detail. For now, any filters must be explicitly specified with every call to ConnectToApplication.
I'm not handling content handlers properly yet in this round. TBD.
http://crbug.com/510210
Review URL: https://codereview.chromium.org/1244233002
Cr-Commit-Position: refs/heads/master@{#340352}
Currently, filters are not inherited when a restricted application starts a new application. If I did that immediately there is an opportunity for races if a restricted app starts a trusted app before the trusted broker can. I need to think through that in more detail. For now, any filters must be explicitly specified with every call to ConnectToApplication.
I'm not handling content handlers properly yet in this round. TBD.
http://crbug.com/510210
Review URL: https://codereview.chromium.org/1244233002
Cr-Commit-Position: refs/heads/master@{#340352}
30 files changed: