Closed Bug 1405884 Opened 7 years ago Closed 7 years ago

Isolate indexedDB by OriginAttributes

Categories

(Core :: Storage: IndexedDB, enhancement, P3)

Product:
Core
Component:
Storage: IndexedDB
Type:
enhancement

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: arthur, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [tor]) 

indexedDB is a supercookie vector. We should isolate it by origin attributes. (Currently, Tor Browser disables indexedDB, but in the future, we would like to support a memory-only, clearable, first-party isolated indexedDB.)
Priority: -- → P3
IDB is already isolated. Open a nilla profile, set FPI=true, visit YT and watch ~/profile/storage/default entries like: https+++www.youtube.com^firstPartyDomain=youtube.com

Or am I missing something here?

> we would like to support a memory-only, clearable, first-party isolated indexedDB

that excludes `moz-extension+++`* entries - FTFY
I confirm. IndexedDB uses QuotaManager, and QuotaManager supports OriginAttributes.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
That's great! Sorry for not realizing this already.
Yes, it's isolated.
(In reply to Andrea Marchesini [:baku] from comment #2)
> I confirm. IndexedDB uses QuotaManager, and QuotaManager supports
> OriginAttributes.

For reference, this got done in bug 1278037 I believe.
You need to log in before you can comment on or make changes to this bug.