New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 623397 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Aug 2016
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Eliminate concept of outgoing InterfaceProvider on Connect()

Project Member Reported by ben@chromium.org, Jun 26 2016

Issue description

The Connector::Connect() API provides for an outgoing InterfaceProvider, which allows the connecting app to expose interfaces to the connectee. We use this in a couple of places, including the tracing service & (eventually) the browser launching the renderer.

This muddles the security policy a little bit, as there's currently no checking on what interfaces get exposed on the outgoing provider, in accordance with CapabilitySpec.

We should eliminate this outgoing provider, and require that connectees connect back to the connecting app to request interfaces, which will trigger all the appropriate policy checks.
 

Comment 1 by ben@chromium.org, Aug 16 2016

Status: Fixed (was: Assigned)

Sign in to add a comment