vissha Posted July 28, 2018 Share Posted July 28, 2018 Mozilla plans to change the updating logic of Firefox by removing the option to block updates from the browser's user interface and from about:config. Current stable versions of the Firefox web browser support three states when it comes to checking for and installing updates in the web browser. The default setting checks for updates automatically and installs them immediately when found. The second state checks for updates but requires user interaction to start the installation of the update, and the third state disables update checking entirely in the browser. Firefox users can open about:preferences#general in the browser and scroll down to the Firefox Updates section to manage update settings in the Firefox browser. Firefox users could also set the preference app.update.enabled on about:config to false to disable update checks in the browser. Mozilla plans to change the updating logic of Firefox by removing the third option from the browser's user interface and from about:config. The organization does not mention explicitly how it plans to deal with Firefox installations that are set to never check for updates. It seems likely that the setting will be switched to "check but don't install" automatically, but that is not mentioned explicitly anywhere. Firefox users who have set the browser to never check for updates should verify which setting is enabled after upgrading to version 63. Firefox 63 is scheduled to release in October 2018. Why is Mozilla making the change? The bug listing on [email protected] highlights that the option is "easy to enable and forget about", and that it "contributes to orphaned users" and "exposes users to severe security issues". The new method The feature won't be removed entirely, however. The recently introduced policy engine provides an option to block updates in Firefox entirely. Firefox users and system administrators have two options to use policies. They can create a policies.json file manually and fill it with appropriate policies, or use the excellent Enterprise Policy Generator instead. Just install the extension in the Firefox web browser and open its settings with a click on the icon. Locate Updates & Data Collection and check the policy "Prevent Firefox from updating". The policy requires Firefox ESR 60 or higher, or Firefox 62 or higher. The add-on creates a policy file that you need to place in the distribution folder of the Firefox installation. Additional information about policy support is available here. Closing Words While it is generally not recommended to disable the installation of updates, it should be up to the user to make that decision in my opinion. Yes, it would be great if all users would run the latest version of Firefox but users have multiple reasons for not wanting to update. While it is more difficult to block update checking entirely in Firefox, an option to do so still exists even in Firefox 63 and future versions released after Firefox 63. Now You: How do you handle updates in Firefox? (via Deskmodder / Sören Hentzschel) Source PS-2: The current Mozilla devs should understand that if the browser updates are good without ruining the features/non-buggy, most users would update even if check for updates are set to never check.PS-1: It is very sad about Mozilla & Firefox development in the recent months - Very Worse and Worrying Changes! "Real Mozilla Firefox" Fans should improvise Waterfox/Palemoon/push to continue Cyberfox developments or should try to create a better Gecko browser instead of Chromium/Qt engine. Link to comment Share on other sites More sharing options...
Karlston Posted July 28, 2018 Share Posted July 28, 2018 Users: WE want to be able to block updates to OUR Firefox installs. Mozilla: Users don't want to block updates to OUR installs. --- Sounds like too many laggards are still choosing to run old versions. How dare they, the impudent wretches! Mozilla brings to Firefox one of the worst Windows 10 features, forced updates. What is it about tech companies becoming update-control-freaks? Time to blacklist Mozilla's update servers. Anyone know the domains? Firefox update blocked by firewall is a couple of years old but has "aus" in the domain names. May be Australia specific servers? For the record, this laggard is still running Firefox 56.0.2. Why? Because WebExtensions still don't give me the same functionality that the "old" add-ons do. Link to comment Share on other sites More sharing options...
coromonadalix Posted July 29, 2018 Share Posted July 29, 2018 well time to let go of it, since the change in the pluggin "technology", i began to search alternatives .. very deceived to say the least The problems now with the Firefox Esr ones, many websites try to impose the latest versions ... if it's too low it wont permit any entry / access arrrrrrrrrrrrrrr Link to comment Share on other sites More sharing options...
pc71520 Posted July 30, 2018 Share Posted July 30, 2018 Quote Mozilla makes it more difficult to block Firefox updates Following the Windows 10 path... Link to comment Share on other sites More sharing options...
debebee Posted July 30, 2018 Share Posted July 30, 2018 15 hours ago, coromonadalix said: well time to let go of it, since the change in the pluggin "technology", i began to search alternatives .. very deceived to say the least The problems now with the Firefox Esr ones, many websites try to impose the latest versions ... if it's too low it wont permit any entry / access arrrrrrrrrrrrrrr That is the reason why i have multiple firefox (portables) An old ESR for old-plugins And the latest one for the picky sites And portables have made it possible not to install the mozille update service Link to comment Share on other sites More sharing options...
dcs18 Posted July 30, 2018 Share Posted July 30, 2018 As long as Mozilla doesn't depreciate the corresponding about:config entries that are responsible for enabling/disabling program updates, I'm not grumpy. However, gotta say that it sure is unfair on less knowledgeable users whenever any existing option is no longer made available on the GUI. A cursory check of my system reveals the following about:config entries that disable Firefox program (there could be more — too lazy to do a more thorough check):— Quote ("app.update.auto", false) ("app.update.enabled", false) ("app.update.interval", 0) ("app.update.lastUpdateTime.datareporting-healthreport-lastDailyCollection", 0) ("app.update.service.enabled", false) ("app.update.silent", false) ("app.update.mode", 1) Apart from the about:config, my personal preference to disable program updates is the trusty firewall — the following IPs can be safely blocked:— Quote 63.245.215.111 63.245.217.44 63.245.217.137 63.245.217.138 69.195.141.178 69.195.141.179 82.103.140.40 82.103.140.42 ps:— Firewalls take no shit from Developers who decide to make existing options unavailable on the GUI — they give no shit, either. Link to comment Share on other sites More sharing options...
BimBamSmash Posted August 7, 2018 Share Posted August 7, 2018 Any reasons why people wish not to update their Firefox, beyond that extension system overhaul? Link to comment Share on other sites More sharing options...
Ecarion Posted August 7, 2018 Share Posted August 7, 2018 lockPref("app.update.enabled",false); Apparently, it doesn't exist anymore... and you could try to (re)create this one but no it won't work (even with a new profil). That's why it doesn't work and I had discover this trouble 2 days ago (with Firefox_v63 aka Nightly). Damn it Mozilla this time the blame will come soon... Because it's another wrong decision and the Bad Wolf is very very very close. lockPref("app.update.auto",false); lockPref("app.update.enabled",false); lockPref("app.update.service.enabled",false); In fact @dcs18 you don't need to check. Because it will be useless (only these 3 settings must be disable) and I'm able to confirm : yes it work's fine since several years. Link to comment Share on other sites More sharing options...
dcs18 Posted August 8, 2018 Share Posted August 8, 2018 @Ecarion Well, each and every one of those 7 entries are very much present (and relevant) on the about:config of my Firefox ESR 52.9.0. If they don't exist on your copy — I'm afraid, you might be running a version which is stealing granularity of control from Users. Link to comment Share on other sites More sharing options...
Ecarion Posted August 8, 2018 Share Posted August 8, 2018 No you made a mistake @dcs18 (about the meaning) because I wasn't talking about their existence. In fact, it's just one (little) explanation about : How proceed to disable the automatic update ? Because a lot of people rather to update manually or to keep one old good version of Firefox. That's why I will wait before to migrate (Firefox Quantum). It was published too soon and it won't be ready until a very long while sic... Unless Mozilla : rectify this trouble ? start to really listen the people ? and learn from their errors ? Almost one year (Firefox-v57 ? Indeed it's remain only 3 months because it was published in November) and today it's even worst (another bad news or bad choice) because damn it : I want the full control. That's why finally I will probably very soon abandon Nightly. Link to comment Share on other sites More sharing options...
debebee Posted August 8, 2018 Share Posted August 8, 2018 http://www.updatefreezer.org/ does a good job for the average joe to stop automatic updates of firefox and similar software Link to comment Share on other sites More sharing options...
Ecarion Posted October 6, 2018 Share Posted October 6, 2018 Finally there is a good news. Because I had discover recently one solution (to rectify this trouble). { "policies": { "DisableAppUpdate": true } } Create a folder called "distribution" Then create a file "policies.json" Recopy the code Restart (the browser) Firefox Otherwise you can use the addon Enterprise Policy Generator. Because it will help to generate this file and as today there is a bunch of settings... Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.