3 ms·

I don't understand why renewing the certificate wouldn't fix the issue ? How does the 66.0.4 fix the problem exactly ?

• kam 8y 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 8y ago
    That 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 8y 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 ?
    • db48x 8y ago
      Two years, iirc.
    • acqq 8y ago
      Don't know about the old one, but the new one from the patch is: Not Before: Apr 4 00:00:00 2015 GMT Not After : Apr 4 00:00:00 2025 GMT
  • raverbashing 8y ago
    So 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