Closed Bug 942385 Opened 11 years ago Closed 10 years ago

Restrict identity assertions to noaccess/peerIdentity constrained tracks only

Categories

(Core :: WebRTC, defect)

Product:
Core
Component:
WebRTC
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: mt, Unassigned)

References

Details

We should not be providing identity assertions on sessions that contain media that has been seen or touched by a site.

This gets tricky because it also means that we need to block the addition (or at least transmission) of un-constrained tracks, either those that are added via new streams or via tracks that are added to streams.  It also means that you can't remove the peerIdentity constraint from a stream once it is attached to an RTCPeerConnection.
Not going to do this.  We want to be able to surface identity information, even if a site doesn't request isolated media.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.