Open Bug 1589685 Opened 6 years ago Updated 1 year ago

Use StoragePrincipal for deviceId (and potentially QuotaManager if not used)

Categories

(Core :: WebRTC, enhancement, P3)

Product:
Core
Component:
WebRTC
Type:
enhancement

Tracking

()

People

(Reporter: annevk, Unassigned)

References

(Blocks 1 open bug)

Details

Per discussion with Jan-Ivar, StoragePrincipal is not used for deviceId at the moment which would allow circumventing some storage policies potentially.

In particular, if a user uses top-level A and A nested in top-level B (with B delegating permission once we have Feature Policy) the two As should probably not get to bypass StoragePrincipal separation even if they both have a WebRTC permission.

Flags: needinfo?(jib)

Very good point, happy to help integrate this with storage principal.

Jib, can you please follow up on the above?

Type: defect → enhancement
Priority: -- → P3
Blocks: 1590107
Severity: normal → S3
Flags: needinfo?(jib)
Priority: P3 → P2
Priority: P2 → P1
Blocks: webrtc-triage
Priority: P1 → P3

smaller issue now that more privacy oriented enumerate devices shipped.

No longer blocks: webrtc-triage
You need to log in before you can comment on or make changes to this bug.