News for hackers. Stuff that matters.
Re:Firefox 30.0 by TorKlingberg on Tuesday June 10, 2014 @03:52PM (#7874889)
Installers on Windows run with administrator privilege and can do anything they want, including modifying the Firefox binaries. We might end up with an arms race between adware vendors forcing their stuff into Firefox and Mozilla trying to disable it.
Re:Firefox 30.0 by sp332 on Tuesday June 10, 2014 @04:10PM (#7875016)
If an installer modified the binary, Firefox couldn't stop that. What installers actually do is move some plugin files into the global Firefox plugins folder, so they get loaded on next startup. Because you can't uninstall the global plugins from the user's account, they added a per-user setting that keeps track of which "global" plugins that user has allowed.
Re:Firefox 30.0 by MichaelGG on Tuesday June 10, 2014 @07:41PM (#7875928)
That wouldn't be anything new, and the system's malware detection should help. Although it's a hard problem if users insist on running random binaries, of course.
Re:Firefox 30.0 by jhasse on Tuesday June 10, 2014 @04:01PM (#7874953)
"Installers on Windows run with administrator privilege"

That's what's wrong with Windows and most desktop Linux distros.

Re:Firefox 30.0 by fulafel on Tuesday June 10, 2014 @04:31PM (#7875136)
If they ran with user privilege, they could still stomp on each other.
Re:Firefox 30.0 by r00fus on Wednesday June 11, 2014 @01:53AM (#7876642)
The OSX preferred app install process (used by FF) is simply to download the disk image, and move your app to the /Applications folder.

The Mac App Store likely also prevents apps from clobbering other apps' folders while installing.

I try to avoid software the requires an installer if at all possible.

Re:Firefox 30.0 by jhasse on Sunday June 15, 2014 @04:04PM (#7896135)
There should be sandboxing / requesting priveleges like Android has it.