Isolating Browser State with Firefox Multi-Account Containers
Stop juggling browser profiles. Learn how to use Firefox Multi-Account Containers to isolate cookies and storage for multiple accounts and improved privacy.
Loading…
ReadMeFeed / Community knowledge
#browser-security
Real questions. Useful conversations. Find the people who know your stack.
Understanding Chrome Site Isolation: Why Your Browser Uses So Much RAM
Explore how Chrome's Site Isolation architecture prevents speculative execution attacks like Spectre by moving the security boundary from the tab to the site, and why this increases RAM usage.
chromeOpera's Native Ad Blocker: Trading Extension Flexibility for Core-Level Speed
Opera's built-in ad blocker filters ads in native C++ using EasyList and EasyPrivacy, avoiding the overhead of JavaScript extensions. Here is how it works, how to verify it, and when to stick with an extension instead.
operaArchitecting for Chrome Site Isolation: Trust Boundaries and Process Separation
Learn how Chrome Site Isolation separates renderer processes to prevent cross-site memory leaks and how to verify these boundaries using internal diagnostics.
Chrome Site Isolation Architecture: Requirements, Minimal Design, Boundaries, Checks, and When to Reconsider
Explains Chrome Site Isolation’s requirements, minimal renderer‑per‑site design, trust boundaries, operational checks, failure modes, and when the design might change.
How Chrome’s Site Isolation Keeps Your Tabs Separate and What It Costs
Learn how Chrome’s Site Isolation isolates each website into its own renderer process, how to verify it, and what trade‑offs to expect.
Enable Chrome Site Isolation for Stronger Site‑to‑Site Security
Learn how to turn on Chrome’s Site Isolation feature to run each website in its own renderer process, improving security and limiting cross‑site attacks.
Firefox Site Isolation (Project Fission): Architecture, Trade-offs, and Operational Reality
Firefox's Project Fission (Firefox 93+) isolates cross-origin documents into separate OS processes to mitigate Spectre-class attacks. Covers per-eTLD+1 design, IPC bridges, trust boundaries, verification via about:processes, failure modes, and future design pressures.
firefoxRemote debugging port binding limits in puppeteer.launch
Browser Control Surface Exposure When initializing a browser instance via puppeteer.launch , the library allows the configuration of Chromium launch arguments. A critical security consideration involves the remote debugging port, which provides an unauthenticated interface for browser control. While Puppeteer manages the browser process, the binding of this
puppeteer