We’re investigating an issue with a certificate which may cause your extensions to stop work working or fail to install. Our team is actively working to fix the issue and we’ll post more information shortly.”
Mozilla took to Twitter to explain: “We’re investigating an issue with a certificate which may cause your extensions to stop work working or fail to install. Taking a look at the about:addons page (reachable at Tools → Add-ons → Unsupported from the menu bar) yielded nothing further, according to Paul Ducklin, security researcher at Sophos - only the terse message specifically pointing at NoScript: “NoScript could not be verified for use in Tor Browser and has been disabled.” Thus also on Friday, upon launching the privacy-minded Onion Router, Tor users began receiving the message, “One or more installed add-ons cannot be verified and have been disabled,” with no further explanation. Mozilla doesn’t allow unsigned add-ons in the Firefox browser, and because Tor is based on Firefox, the same rule applies. check your connection,’ even when I have a very good internet and when the extension downloads, it says, ‘addon could not be installed, it seems to be corrupted,'” one user reported. “Firefox sometimes says, ‘download failed. Starting on Friday, Firefox users took to the discussion boards to report and complain about the issue, which prevented not just NoScript, but all other add-ons to load as well. It’s officially trusted by Mozilla and Tor, but it’s also used in other browsers. NoScript is a Java-blocker that prevents active content from running if it’s from untrusted sites, and it protects users against cross-site scripting (XSS) and other web security exploits. A fix is available for Firefox, but the Tor issue continues. Thanks to Mozilla letting an intermediate signing certificate expire, the Tor community was thrown into disarray over the weekend when the NoScript security add-on was suddenly killed for both Firefox and the Tor browser.
0 kommentar(er)
