[w3c/IndexedDB] SSD wear: does it sound like a real risk? (Issue #511)

Josh-Cena created an issue (w3c/IndexedDB#511)

Hi! MDN editor here.

I'm triaging the issue https://github.com/mdn/content/issues/44590, which says there may be a risk with IndexedDB/OPFS in that they allow sites to, without user consent, modify the file system at a very high throughput, and may wear down the SSD in the process.

I've never heard of it being an identified attack vector or that there's any motive for anyone to do so, but it does sound like something users can be concerned with.

Has the WG ever thought about how implementations could help mitigate this, such as options to lower the threshold, rate-limit, buffer in memory, etc.? I didn't find related considerations in https://w3c.github.io/IndexedDB/#security, but it does look like browsers already buffer IndexedDB in memory.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/511
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/IndexedDB/issues/511@github.com>