1112895 - Design and implement EME equivalent of "Privacy -> Show Cookies" UI to enumerate and remove origins' EME/DRM license information

Status: NEW

(Firefox :: Settings UI, defect)

Description

[Chris Peterson [:cpeterson]]

merwin says this UI is not an EME ship blocker.

Comment 1

[Justin Dolske [:Dolske]]

What's the intended usecase(s)?

I am little dubious about the value of this UI. The only general use I can think of is to help surface the fact that such data exists (but the actual data itself seems unlikely to be useful).

We're already lacking in this department (eg localstorage, indexdb, site permissions), so if we do anything here it might be more useful to do it as a more general "site-specific settings" UI. (Perhaps vaguely akin to about:permissions, but that's deprecated.)

Comment 2

[Chris Peterson [:cpeterson]]

(In reply to Justin Dolske [:Dolske] from comment #1)
> What's the intended usecase(s)?
> 
> I am little dubious about the value of this UI. The only general use I can
> think of is to help surface the fact that such data exists (but the actual
> data itself seems unlikely to be useful).

Yes, the use case is pretty much to see which origins have deposited "DRM cookies" and to delete them. The actual data is not useful; these are literally random numbers (SHA-256 hashes of machine-unique identifiers and a random salt value).

Comment 3

[Chris Pearce [:cpearce (Not reading bugmail)]]

(In reply to Chris Peterson [:cpeterson] from comment #2)
> (In reply to Justin Dolske [:Dolske] from comment #1)
> > What's the intended usecase(s)?
> > 
> > I am little dubious about the value of this UI. The only general use I can
> > think of is to help surface the fact that such data exists (but the actual
> > data itself seems unlikely to be useful).
> 
> Yes, the use case is pretty much to see which origins have deposited "DRM
> cookies" and to delete them. The actual data is not useful; these are
> literally random numbers (SHA-256 hashes of machine-unique identifiers and a
> random salt value).

If we delete the salt values we should also delete the data stored for the origins to which the salt corresponds, as without the origin -> salt mapping (that we just deleted) the stored data is no longer accessible, and will leak on disk.

Therefore, this bug should be "delete all data associated with DRM/EME", not just the salt values.