5 stories
eMudhra will withdraw from issuing public TLS certificates, keeping revocation services running until every issued certificate has expired or been replaced. Customers get replacements free through partners.
In the thread, a commenter reports that an up-to-date iPhone was still trusting the compromised CAs nearly five days after the report.
The top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.
The change is about extension architecture, not a new Firefox feature. For users who depend on uBlock Origin, the browser has become a practical refuge from restrictions rolling through Chrome-derived products.
HN commenters also pointed to Brave and custom extensions, but the broader complaint was simpler: modern advertising has made blocking it feel necessary for ordinary browsing.
Open admin.google.com in Firefox and a security banner appears: secure your device, download Chrome, sign in with your work account. No technical reason was visible for the demand.
The blog's author turned up in the thread to confirm he is the admin, has never enabled Identity-Aware Proxy, and is on Workspace Business Plus, where Google's Context-Aware Access browser lock isn't even available. So what is triggering it?
Chrome 150 (around June 30, 2026) drops the ExtensionManifestV2Disabled flag; Chrome 151 in July removes the rest. Google cites "complexity, tech debt, and security risks."
A self-identified Googler defended it as a security move. A reply noted Google makes 75% of its revenue from ads — and controls the extension store it claims to be protecting.
Manifest V2 was already off by default since Chrome 138 last July. What dies now is the last enterprise-and-flag workaround that let technically-minded users re-enable it — uBlock Origin Lite, the Manifest V3 version, keeps far less power to block.
The thread's sharpest line wasn't outrage at Google. It was a Firefox user admitting he still keeps Chrome around because some sites simply won't load right anywhere else.
