Companies basically have three options if they want their software programs to be compatible with Firefox: They can create a Firefox add-on, a plugin, or integrate the program in the components directory directly. The last option caused lots of concern for the Mozilla developers who linked these method to instabilities and crashes in the web browser. The main reason for these was code that was not updated to follow steps with the Firefox development. The code changes in later Firefox versions resulted in these incompatibilities.
Even worse was the fact that Firefox users were not able to manage these components at all as they would not be displayed in the add-on’s and plugin’s section of the web browser. This meant that Firefox users were not able to disable them if they encountered incompatibilities. But the Mozilla developers themselves were also unable to react on incompatible components or those that would pose a security risk to Firefox users. You might remember that they did block a Microsoft plugin globally after a security vulnerability was disclosed but that was a plugin, not something that was added to the components directory.
From Firefox 3.6 Beta 3 on the components directory is locked for third parties. This means that third party programs that were using this way to add their functionality to Firefox are not working anymore since they are blocked by the web browser. Only Mozilla components will from this web browser version on be allowed to use the components directory.
Neowin and others have reported about this but got their facts wrong as they linked this stability and security measure to the Microsoft silent install incident a while ago. Microsoft back then installed two plugins without the user’s consent, something that other software companies like Apple do as well. Microsoft’s bad luck was that a security vulnerability was disclosed shortly thereafter which made the Mozilla developers block the plugin globally for all Firefox users.
The components directory is a subdirectory of the Firefox installation directory.
Related posts:
- Thunderbird And Firefox Plugin Checker
- Microsoft Silently Installing Windows Presentation Foundation Plugin For Firefox
- How To Stop Automatic Plugin Installations In Firefox
- Latest Firefox Nightlies Comes With Multi-Process Support
- Check and Remove Plugins in Firefox
- Mozilla Checks Flash Version After Firefox Updates
- Check Firefox Add-On Compatibility Before Upgrading
- Multi-Process Plugins Enabled In Latest Firefox Nightlies
Hoi Martin as you could read in the second part of main question, in the above article command, i was still a little bit with main thoughts with this article. So i ask main question again but now on the right place : Do I understand it correctly that now malignant components can not be installed any more?
Paulus components cannot be installed by third parties anymore but plugins can. So you got no chance to companies like Microsoft, Google or Apple adding their plugins to Firefox without any notification in the browser. That’s however something that the developers of Firefox should consider implementing, i.e. check for new plugins that have not been there and ask the user for explicit permission before they become active.