How to disable the 'Check for updates' button on FX 52.9 ESR
- c627627
- Posts: 643
- Joined: April 3rd, 2005, 12:58 pm
- Location: Kansas City, Missouri
- Contact:
Re: How to disable the 'Check for updates' button on FX 52.9
I didn't get any hits when I CTRL+F on that forum page so it took me a while to find it, it was in a link that forum in turn linked to, but for others who like me didn't know:
You create file autoconfig.js not inside your profile, but inside
C:\Program Files (x86)\Mozilla Firefox\defaults\pref
(for the example of 32-Bit Fiorefox.)
Now in it, I am not sure what you would place exactly?
Surely just placing
app.update.auto
app.update.enabled
app.update.service.enabled
in it would not flip them to FALSE?
(Sorry for asking for your time to spell it out.)
You create file autoconfig.js not inside your profile, but inside
C:\Program Files (x86)\Mozilla Firefox\defaults\pref
(for the example of 32-Bit Fiorefox.)
Now in it, I am not sure what you would place exactly?
Surely just placing
app.update.auto
app.update.enabled
app.update.service.enabled
in it would not flip them to FALSE?
(Sorry for asking for your time to spell it out.)
Open the pod bay doors, Cortana.
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: How to disable the 'Check for updates' button on FX 52.9
That seems correct.You create file autoconfig.js not inside your profile, but inside
C:\Program Files (x86)\Mozilla Firefox\defaults\pref
(for the example of 32-Bit Fiorefox.)
I'm thinking, only this:Now in it, I am not sure what you would place exactly?
Code: Select all
// autoconfig.js file needs to start with a comment
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
Then it seems, if I'm understanding (& I've always had trouble understanding anything posted on SUMO), you add your wanted changed prefs (or JavaScript code) into mozilla.cfg (which goes into FF's instalDir).
"Prefs" are formatted similar to the way they show up in prefs.js.
So seemingly mozilla.cfg would be:
Code: Select all
pref("app.update.auto", false);
pref("app.update.enabled", false);
pref("app.update.service.enabled", false);
Anyhow, plug it in & try it.
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
- lovemyfoxy
- Posts: 2337
- Joined: December 11th, 2009, 11:23 am
- Location: USA
Re: How to disable the 'Check for updates' button on FX 52.9
I work online, and occasionally I lose out on a task because my 52ESR is not "up-to-date.The Tinsmith wrote:...
Maybe you are experienced enough to remember when some websites would not let you on if your browser was 'out of date'? Or not an IE version?
2 Desktops--Win 7 Ult.SP1 x64/6GB RAM /Firefox 52.9ESR/Waterfox64 2022.11/Thunderbird 52.9ESR/BitWarden PW Manager/Verizon FIOS wired network
-
- Posts: 913
- Joined: December 24th, 2011, 10:29 am
Re: How to disable the 'Check for updates' button on FX 52.9
LoveMyFoxy wrote:I work online, and occasionally I lose out on a task because my 52ESR is not "up-to-date.The Tinsmith wrote:...
Maybe you are experienced enough to remember when some websites would not let you on if your browser was 'out of date'? Or not an IE version?
I am not in anyway an expert here but that sounds really, really incorrect. I would report that to Mozilla.
- c627627
- Posts: 643
- Joined: April 3rd, 2005, 12:58 pm
- Location: Kansas City, Missouri
- Contact:
Re: How to disable the 'Check for updates' button on FX 52.9
Yes, ESR 52 was updated yesterday so it's technically the most secure browser there is, which web page won't take it? It takes a long time after end of life, for a Firefox version to be blocked.
Paypal still takes Firefox released four years ago (!) This means we may be looking at 2022/2023 range at least for (not yet even released) ESR 52.9.
therube, I guess this is complicated enough for majority of people to not know how to implement.
I would be glad to test it. Could you tell me what exactly is a successful result of the test, I do have multiple Firefox profiles...
You click on the Update button and nothing happens?
Or do I have to have a previous Firefox version installed, so that there actually IS an update to download and then I test to see if it will download?
Paypal still takes Firefox released four years ago (!) This means we may be looking at 2022/2023 range at least for (not yet even released) ESR 52.9.
therube, I guess this is complicated enough for majority of people to not know how to implement.
I would be glad to test it. Could you tell me what exactly is a successful result of the test, I do have multiple Firefox profiles...
You click on the Update button and nothing happens?
Or do I have to have a previous Firefox version installed, so that there actually IS an update to download and then I test to see if it will download?
Open the pod bay doors, Cortana.
- James
- Moderator
- Posts: 28005
- Joined: June 18th, 2003, 3:07 pm
- Location: Made in Canada
Re: How to disable the 'Check for updates' button on FX 52.9
The most secure web browser option for WinXP/Vista yes but not overall. ESR is all about stability so this means not all security fixes that goes in Releases will necessarily go in ESR channel builds.c627627 wrote:Yes, ESR 52 was updated yesterday so it's technically the most secure browser there is, which web page won't take it? It takes a long time after end of life, for a Firefox version to be blocked.
Paypal still takes Firefox released four years ago (!) This means we may be looking at 2022/2023 range at least for (not yet even released) ESR 52.9.
Paypal will be looking for Firefox 49.0 (released September 20, 2016) or later versions so not quite over four years ago. https://www.paypal.com/us/smarthelp/art ... er-faq3893
- lovemyfoxy
- Posts: 2337
- Joined: December 11th, 2009, 11:23 am
- Location: USA
Re: How to disable the 'Check for updates' button on FX 52.9
The Tinsmith wrote: I am not in anyway an expert here but that sounds really, really incorrect. I would report that to Mozilla.
Mozilla isn't the problem, the site I work for is, and they see it's 52. I switched to Chrome just for that one site. I hold my nose and scrub the machine with bleach after each use.
2 Desktops--Win 7 Ult.SP1 x64/6GB RAM /Firefox 52.9ESR/Waterfox64 2022.11/Thunderbird 52.9ESR/BitWarden PW Manager/Verizon FIOS wired network
- Benjamin Markson
- Posts: 397
- Joined: November 19th, 2011, 3:57 am
- Location: en-GB
Re: How to disable the 'Check for updates' button on FX 52.9
You might look at these two add-ons. They allow you to decide the User Agent version you present to each web site you visit.LoveMyFoxy wrote:Mozilla isn't the problem, the site I work for is, and they see it's 52. I switched to Chrome just for that one site. I hold my nose and scrub the machine with bleach after each use.
https://addons.mozilla.org/en-GB/firefo ... /uacontrol
https://addons.mozilla.org/en-GB/firefo ... t-js-fixer
The most picky sites I've come across so far are mozilla.net and mozilla.org ...go figure.
Ben.
XUL is dead. Long live the Google Chrome Clones.
-
- Posts: 4480
- Joined: March 19th, 2005, 10:51 am
Re: How to disable the 'Check for updates' button on FX 52.9
there is nothing wrong with the IA from 52esr. waste of ressources to fake this. and if paypal restricts access due ssl/tls no UA can help out because firefox cant handle it.
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: How to disable the 'Check for updates' button on FX 52.9
I would suppose that on opening a new Profile, going into about:config, those Prefs should be at non-default settings, should show as 'false'.Could you tell me what exactly is a successful result of the test
And assuming that to be the case, you would expect updates to not occur.
On an existing Profile, not sure?
In existing, leave or set the Prefs to 'true'.
Close FF & reopen.
True or false?
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: How to disable the 'Check for updates' button on FX 52.9
I'm not sure that is correct.ESR is all about stability so this means not all security fixes that goes in Releases will necessarily go in ESR channel builds.
AFAIK, all appropriate security fixes from releases get backported.
(If an security fix from release does not apply to ESR, like because a particular feature was never implemented in ESR, then in a case like that, there is nothing to backport to.)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
- Frank Lion
- Posts: 21178
- Joined: April 23rd, 2004, 6:59 pm
- Location: ... The Exorcist....United Kingdom
- Contact:
Re: How to disable the 'Check for updates' button on FX 52.9
How are PayPal going to restrict access when PayPal will only require TLS 1.1 and SeaMonkey 2.49.3 and Firefox 52 already support TLS 1.3?Brummelchen wrote:there is nothing wrong with the IA from 52esr. waste of ressources to fake this. and if paypal restricts access due ssl/tls no UA can help out because firefox cant handle it.
"The only thing necessary for the triumph of evil, is for good men to do nothing." - Edmund Burke (attrib.)
.
.
- c627627
- Posts: 643
- Joined: April 3rd, 2005, 12:58 pm
- Location: Kansas City, Missouri
- Contact:
Re: How to disable the 'Check for updates' button on FX 52.9
Also, we had many emergency Firefox security updates which were not issued for ESR _because_ ESR was not affected, technically meaning Firefox ESR was _more_ secure than Firefox regular? In other words if you were using (most updated) ESR all that time you were fine, but if you were using Firefox regular, you were at risk.
the rube, this did NOT work, we need more help, this is a difficult thing to figure out:
1. You create file autoconfig.js not inside your profile, but inside
C:\Program Files (x86)\Mozilla Firefox\defaults\pref
(for the example of 32-Bit Firefox.)
2. Contents of autoconfig.js are:
// autoconfig.js file needs to start with a comment
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
3. You create a mozilla.cfg file inside
C:\Program Files (x86)\Mozilla Firefox
(for the example of 32-Bit Firefox.)
4. Contents of mozilla.cfg file are:
pref("app.update.auto", false);
pref("app.update.enabled", false);
pref("app.update.service.enabled", false);
5. RESTART Firefox
Now this still UPDATED Firefox 52.8.0 to 52.8.1
even though about:config clearly shows all these values to be FALSE:
app.update.auto
app.update.enabled
app.update.service.enabled
We need more help on what to do differently to disable not just the existence of the 'check for updates button' which we can do.
But its functionality as well since it can be run from another profile where this button was not removed.
I am standing ready to test anything else anyone suggests.
the rube, this did NOT work, we need more help, this is a difficult thing to figure out:
1. You create file autoconfig.js not inside your profile, but inside
C:\Program Files (x86)\Mozilla Firefox\defaults\pref
(for the example of 32-Bit Firefox.)
2. Contents of autoconfig.js are:
// autoconfig.js file needs to start with a comment
pref("general.config.filename", "mozilla.cfg");
pref("general.config.obscure_value", 0);
3. You create a mozilla.cfg file inside
C:\Program Files (x86)\Mozilla Firefox
(for the example of 32-Bit Firefox.)
4. Contents of mozilla.cfg file are:
pref("app.update.auto", false);
pref("app.update.enabled", false);
pref("app.update.service.enabled", false);
5. RESTART Firefox
Now this still UPDATED Firefox 52.8.0 to 52.8.1
even though about:config clearly shows all these values to be FALSE:
app.update.auto
app.update.enabled
app.update.service.enabled
We need more help on what to do differently to disable not just the existence of the 'check for updates button' which we can do.
But its functionality as well since it can be run from another profile where this button was not removed.
I am standing ready to test anything else anyone suggests.
Open the pod bay doors, Cortana.
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: How to disable the 'Check for updates' button on FX 52.9
In the dslreports thread, above Frodo's post is my link to my thread here, which others frown upon, which IMO is very simple method, that seems to work .
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: How to disable the 'Check for updates' button on FX 52.9
No, all you can say is that ESR was not susceptible to particular security exploits that did affect later versions.technically meaning Firefox ESR was _more_ secure than Firefox regular?
There have been plenty of exploits against Windows OS > XP, but hat does not mean that XP is more secure then later OS.
(And yes, I use XP. And Win7.)
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript