Open
Bug 1859558
Opened 1 year ago
Updated 1 year ago
QuotaManager to own the set of CipherKeyManagers for all quota clients.
Categories
(Core :: Storage: Quota Manager, task, P3)
Core
Storage: Quota Manager
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox120 | --- | affected |
People
(Reporter: hsingh, Assigned: hsingh)
Details
In private browsing, cipher keys required for encryption/decryption is managed by quota clients themselves (like IndexedDB (DatabaseFileManager) and CacheAPI (QuotaClient)). However, it's worth exploring an alternative where QuotaManager manages cipherKeys for all quota clients which could be partitioned by a combination of origin string, database name and a quota client type and could contain accessors like QuotaManager::GetOrCreateCipherManager(aOrigin, aClientType, aDatabaseName)
|
Assignee | |
Updated•1 year ago
|
Assignee: nobody → hsingh
|
||
Updated•1 year ago
|
Severity: -- → S4
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•