<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic OPFS usage per origin in the DevTools Storage Inspector in Discussions</title>
    <link>https://connect.mozilla.org/t5/discussions/opfs-usage-per-origin-in-the-devtools-storage-inspector/m-p/127106#M50324</link>
    <description>&lt;P&gt;I was triggered to request this new feature because of this research paper (&lt;A href="https://hannesweissteiner.com/pdfs/frost.pdf" target="_blank" rel="noopener"&gt;https://hannesweissteiner.com/pdfs/frost.pdf&lt;/A&gt;) about yet another new tracking technique: timing the speed of the users SSD via OPFS.&amp;nbsp;See also the discussion on HN here:&amp;nbsp;&lt;A href="https://news.ycombinator.com/item?id=48309492" target="_blank" rel="noopener"&gt;https://news.ycombinator.com/item?id=48309492&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;The Origin Private File System (OPFS) API allows websites to store potentially large files on a user's device — in some cases up to 60% of available disk space. Recent research has shown that this can be exploited as a side-channel attack vector: by timing OPFS I/O operations, a malicious site can infer what other websites or applications a user has running (see: &lt;A href="https://arstechnica.com/security/2026/05/websites-have-a-new-way-to-spy-on-visitors-analyzing-their-ssd-activity/" target="_blank" rel="noopener"&gt;https://arstechnica.com/security/2026/05/websites-have-a-new-way-to-spy-on-visitors-analyzing-their-ssd-activity/&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Firefox currently has two gaps when it comes to OPFS:&lt;/P&gt;&lt;P&gt;1. &lt;STRONG&gt;No DevTools visibility,&lt;/STRONG&gt;&amp;nbsp;Unlike cookies, localStorage, or IndexedDB, OPFS storage used by a website is not shown anywhere in the DevTools Storage Inspector. This makes it impossible for developers and privacy-conscious users to see what a site has written to disk.&lt;/P&gt;&lt;P&gt;2. &lt;STRONG&gt;No user controls&lt;/STRONG&gt;. There is no setting to block OPFS access entirely, nor any option to mitigate the timing side-channel by injecting artificial jitter into OPFS read/write latency (similar to how Firefox already adds noise to certain APIs like canvas and AudioContext to prevent fingerprinting).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Requested improvements:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;- Show OPFS usage per origin in the DevTools Storage Inspector, with the ability to inspect and delete stored files.&lt;BR /&gt;- Add a permission or privacy setting to block or restrict OPFS access, either globally or per site.&lt;BR /&gt;- Add random timing noise to OPFS operations to neutralize SSD-based side-channel attacks, consistent with Firefox's existing anti-fingerprinting approach.&lt;/P&gt;&lt;P&gt;These changes would bring OPFS in line with how Firefox already handles other storage APIs, and would meaningfully improve user privacy against an emerging class of attacks.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jun 2026 13:15:06 GMT</pubDate>
    <dc:creator>TheJanManShow</dc:creator>
    <dc:date>2026-06-01T13:15:06Z</dc:date>
    <item>
      <title>OPFS usage per origin in the DevTools Storage Inspector</title>
      <link>https://connect.mozilla.org/t5/discussions/opfs-usage-per-origin-in-the-devtools-storage-inspector/m-p/127106#M50324</link>
      <description>&lt;P&gt;I was triggered to request this new feature because of this research paper (&lt;A href="https://hannesweissteiner.com/pdfs/frost.pdf" target="_blank" rel="noopener"&gt;https://hannesweissteiner.com/pdfs/frost.pdf&lt;/A&gt;) about yet another new tracking technique: timing the speed of the users SSD via OPFS.&amp;nbsp;See also the discussion on HN here:&amp;nbsp;&lt;A href="https://news.ycombinator.com/item?id=48309492" target="_blank" rel="noopener"&gt;https://news.ycombinator.com/item?id=48309492&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;The Origin Private File System (OPFS) API allows websites to store potentially large files on a user's device — in some cases up to 60% of available disk space. Recent research has shown that this can be exploited as a side-channel attack vector: by timing OPFS I/O operations, a malicious site can infer what other websites or applications a user has running (see: &lt;A href="https://arstechnica.com/security/2026/05/websites-have-a-new-way-to-spy-on-visitors-analyzing-their-ssd-activity/" target="_blank" rel="noopener"&gt;https://arstechnica.com/security/2026/05/websites-have-a-new-way-to-spy-on-visitors-analyzing-their-ssd-activity/&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Firefox currently has two gaps when it comes to OPFS:&lt;/P&gt;&lt;P&gt;1. &lt;STRONG&gt;No DevTools visibility,&lt;/STRONG&gt;&amp;nbsp;Unlike cookies, localStorage, or IndexedDB, OPFS storage used by a website is not shown anywhere in the DevTools Storage Inspector. This makes it impossible for developers and privacy-conscious users to see what a site has written to disk.&lt;/P&gt;&lt;P&gt;2. &lt;STRONG&gt;No user controls&lt;/STRONG&gt;. There is no setting to block OPFS access entirely, nor any option to mitigate the timing side-channel by injecting artificial jitter into OPFS read/write latency (similar to how Firefox already adds noise to certain APIs like canvas and AudioContext to prevent fingerprinting).&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Requested improvements:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;- Show OPFS usage per origin in the DevTools Storage Inspector, with the ability to inspect and delete stored files.&lt;BR /&gt;- Add a permission or privacy setting to block or restrict OPFS access, either globally or per site.&lt;BR /&gt;- Add random timing noise to OPFS operations to neutralize SSD-based side-channel attacks, consistent with Firefox's existing anti-fingerprinting approach.&lt;/P&gt;&lt;P&gt;These changes would bring OPFS in line with how Firefox already handles other storage APIs, and would meaningfully improve user privacy against an emerging class of attacks.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jun 2026 13:15:06 GMT</pubDate>
      <guid>https://connect.mozilla.org/t5/discussions/opfs-usage-per-origin-in-the-devtools-storage-inspector/m-p/127106#M50324</guid>
      <dc:creator>TheJanManShow</dc:creator>
      <dc:date>2026-06-01T13:15:06Z</dc:date>
    </item>
  </channel>
</rss>

