4 ms·
It's a signing certificate that is built into the browser to verify add-ons, not a normal TLS certificate that they can just update on a web server. The change
by kam 7y ago
It's a signing certificate that is built into the browser to verify add-ons, not a normal TLS certificate that they can just update on a web server.
The change basically just imports the new certificate into the database:
https://hg.mozilla.org/releases/mozilla-release/rev/848b15028562c6757748070f637e0e4f0bbb5f65 https://hg.mozilla.org/releases/mozilla-release/rev/848b1502...
- floatingatoll 7y agoThat is not a complete statement of the changes shown. In addition to the unexpired certificate, it takes step to reenable any addons that were disabled by the expiration of the prior certificate.
- johnchristopher 7y ago> It's a signing certificate that is built into the browser to verify add-ons, not a normal TLS certificate that they can just update on a web server. Ah, so that's why. Thanks. What was the signing certificate validity period ?
- raverbashing 7y agoSo are the extensions checked at startup time for disk integrity issues? My extensions on FF have not stopped working but I hadn't restarted the browser in that interim