Chrome's insane password security strategy
Chrome does something interesting when you first run it. — I have a set of bookmarklets that I use to enhance my internet experience. Actually, that's not entirely true. I have one bookmarklet: Embiggen.js, which I use to expand images on Reddit.
Context & Ripple Effects
Elliott Kember's walkthrough shows that Chrome's settings page will display every saved password in plain text on demand, with no request for the operating-system account password first — a few clicks from anyone sitting at an unlocked machine. The post spread unusually fast for a developer-blog item: ZDNet, SiliconANGLE and gHacks all picked it up within a day, and it circulated on Twitter far enough to reach Tim Berners-Lee's account.
The reaction splits along threat-model lines, and the confirmed commentary in circulation is largely critical, framing the design as risky or ill-conceived. Defenders of Chrome argue that anything able to read the settings page already implies local compromise — but Kember's point is that the casual attacker (a colleague, a family member) needs no exploit at all, which is exactly the gap the critique targets.
First-order effects
- Anyone with physical access to an unlocked machine running Chrome can read every stored credential in seconds via the settings page, so users who rely on Chrome's password manager as their sole store are exposed immediately.
Second-order effects
- Rival browser makers face the same question about their own built-in credential stores, since whatever they answer — mask, re-authenticate, or argue local access means game over — becomes a visible differentiator against Chrome.
- Dedicated password-manager vendors gain a ready-made argument for their paid products: a master-password gate that browser-native storage does not impose.
Third-order effects
- If the pattern holds, browser vendors will keep treating physical access as outside their threat model while users assume otherwise — leaving the market for third-party password managers structurally intact rather than absorbed into the browser.
The trend: Browser-native convenience features are colliding with user expectations of security, forcing vendors to defend design choices by threat model rather than by feature checklist.