2 ms·
This appears to be a mistake. It's clearly bad that things can break this way. But this happened because a certificate expired. Mozilla didn't have to require
by jopsen 8y ago
This appears to be a mistake.
It's clearly bad that things can break this way. But this happened because a certificate expired.
Mozilla didn't have to require signatures and certificates for extensions. They did so because they want to protect users.
Protecting users with signature schemes, increase complexity and, thus, the risk of debacles like this.
- thekingofh 8y agoPeople take their privacy seriously. Our addons were disabled. I was browsing for a few minutes until I saw ads and didn't realize what was going on. Unacceptable that the default to an expiring signature is to disable them completely.
- jopsen 8y agoYou would have said the opposite if an expired signature had caused your browser to be compromised!!! The default behavior seems desired to me. The problem was that the certificate was allowed to expire. A have ton of respect for the fact that it was enforced!