-
- Downloads
Bug 14970: Don't block our unsigned extensions
Mozilla introduced extension signing as a way to make it harder for an attacker to get a malicious add-on running in a user's browser. See: https://blog.mozilla.org/addons/2015/02/10/extension-signing-safer-experience and https://blog.mozilla.org/addons/2016/01/22/add-on-signing-update/ for some background information. In ESR45 this feature is enabled by default and we exempt both our own extensions and EFF's HTTPS-Everywhere from this requirement.
Showing
- browser/components/nsBrowserGlue.js 7 additions, 1 deletionbrowser/components/nsBrowserGlue.js
- toolkit/mozapps/extensions/content/extensions.js 8 additions, 0 deletionstoolkit/mozapps/extensions/content/extensions.js
- toolkit/mozapps/extensions/internal/XPIProvider.jsm 14 additions, 0 deletionstoolkit/mozapps/extensions/internal/XPIProvider.jsm
Loading
Please register or sign in to comment