A total of 17 security holes have been addressed by Mozilla with the release of Firefox 36. The latest version of the Web browser also includes support for the HTTP/2 protocol.
While the number of fixed vulnerabilities is higher than usual, only four of the flaws have been rated critical.
Mozilla yesterday detailed plans to require Firefox add-ons to be digitally signed, a move meant to bear down on rogue and malicious extensions, and one that resembled Google's decision years ago to secure Chrome's add-on ecosystem.
Some Firefox users called out Mozilla for disregarding its own long-and-often-expressed ethos of the need for an open Internet.
If you want to find out more about the security of a connection to a particular website or a request that a site made while it was loading, then it is quite difficult to do so right now in most browsers.
While you can look up protocol information if https is used with a click on the lock icon in the browser address bar, and go from there to retrieve additional information, it is taking quite some time to do so.
Since 2004, Google has been paying Mozilla a ton of money each year—estimated at around $100 million—for the privilege of being the default search engine used in the Firefox browser. This contribution represented the lion's share of Mozilla's income, something in the ballpark of 85 percent.
Mozilla today pulled out the PR stops to trumpet the 10th anniversary of Firefox, and in celebration released an interim build of Firefox 33 that includes a new privacy tool and access to the DuckDuckGo search engine.
Firefox 1.0 was released on Nov. 9, 2004, at a time when Microsoft's Internet Explorer (IE) had a stranglehold on the browser space, having driven Netscape -- Firefox's forerunner in many ways -- out of the market two years before. Mozilla has been widely credited with restarting browser development, which had been moribund under IE.