Firefox 3.6 Locks Out Rogue Add-ons 265
CWmike writes "Mozilla will add a new lockdown feature to Firefox 3.6 that will prevent developers from sneaking add-ons into the program, the company said. Dubbed 'component directory lockdown,' the feature will bar access to Firefox's 'components' directory, where most of the browser's own code is stored. Mozilla has billed the move as a way to boost the stability of its browser. 'We're doing this for stability and user control [reasons],' said Johnathan Nightingale, manager of the Firefox front-end development team. 'Dropping raw components in this way was never an officially supported way of doing things, which means it lacks things like a way to specify compatibility. When a new version of Firefox comes out that these components aren't compatible with, the result can be a real pain for our shared users ... Now that those components will be packaged like regular add-ons, they will specify the versions they are compatible with, and Firefox can disable any that it knows are likely to cause problems.'"
I want a mechanism for pluck-outs... (Score:2, Interesting)
At my company I would like a stripped-down Firefox without features like awesome bar and other bloat. Is there a way to do this, easily?
Also I have the SmartQ 7 and SmartQ 5 MIDs which are basedon the ARM processor. Thedefault browseris Midori... can I get a Firefox compiled for the ARM to run on that?
I hink firefox shoudl focus on these and similar issues...
Effects on Add-on Development (Score:3, Interesting)
Or is this just a method to lock out some Add-on with already known problems?
Re:I want a mechanism for pluck-outs... (Score:5, Interesting)
The awesome bar, and most of the other firefox bloat, should be plugins. Firefox had this great plugin architecture which everyone and their dog used- except the firefox devs.
Why doesn't firefox ship with an array of "default" plugins, all of which can be disabled? There's no need for something like awesomebar to be core, is there?
Re:.NET Anyone? (Score:3, Interesting)
It's an artifact of supporting system wide extension installation, rather than per user. Microsoft probably should have used per user installation of the plugin (even though .NET is arguably a system wide update). Removing the support is probably overkill, as I imagine it is useful in managed environments.
It's not that simple (Score:3, Interesting)
Re:.NET Anyone? (Score:2, Interesting)
In my opinion, the missing uninstall button is a Firefox problem. How could they let you install software and list it as is installed software, but provide no method to uninstall?
Simple. Go to your FF address bar and type file:///C: then click on Program Files. You will be faced with a long list of software that FF is claiming is installed on your system, but can't just uninstall. I find it odd that you seem to think a few developers of a piece of software should be able to override the makers of the operating system. Maybe you also think that all the viruses and rootkits and trojans Windows gets from the web is a Firefox problem too?
A while ago there was a fuss about the Dalai Lama's computers getting hacked by Chinese dudes, and one of the guys asked for advice here. The overriding issue was that pretty much any modern software is hackable, if you have a team of experts working on it. MS has such a team, and they chose to target a specific program running within their own operating system - how were the FF devs supposed to stop them? OK, so they make good software, but they can't force you to use a different/better operating system.
Ninite installs only programs you pick? (Score:3, Interesting)
Wow, it's so easy to use! It's almost like having Synaptic for MS Windows programs!