Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

update

more options

I sometimes use my local library for printing, they use firefox browser and i noticed that it was still using version 47, I know that once you open the browser firefox update starts automatically which it does using the library computers, on asking the people in the library they say that the IT dept tells them it is a license problem, how can this be true if firefox starts updating automatically, surely if the machines are left long enough with firefox open they will complete the update, can you please inform me accordingly. Thank you

I sometimes use my local library for printing, they use firefox browser and i noticed that it was still using version 47, I know that once you open the browser firefox update starts automatically which it does using the library computers, on asking the people in the library they say that the IT dept tells them it is a license problem, how can this be true if firefox starts updating automatically, surely if the machines are left long enough with firefox open they will complete the update, can you please inform me accordingly. Thank you

All Replies (3)

more options

Hello, unfortunately, this is up to the Library, and Mozilla can't do anything about this.

more options

I wonder whether they mean that they require a plugin or other older add-on that won't work in a newer version of Firefox??

Some public PCs contain a set configuration that gets replaced every day or at every startup. This prevents a user from installing spyware and capturing personal data of other users over a long period of time, or if things get broken, they are automatically rolled back. So updating may be very temporary if this is the locked configuration.

more options

MY viewpoint is:

The "reason" that occurs to me as to why the library still has Firefox 47 installed is that 47 was the last version that allowed for unsigned addons - and they might be using an old extension that they never bothered to submit to Mozilla for signing. Or Mozilla refused to sign it due to perceived security issues.

I still have Firefox 47 installed and use it daily for specific websites that I trust; 3 extensions that "disappeared" long before signing came about. All are extensions that I "hacked" to keep them working beyond Firefox 3.6 and 4.0 - yeah, that old. None that would pass even the initial screening even back in the days of Firefox 4.0, so I never submitted them for signing knowing there was little chance of getting signed.

Just a guess, though. Seems strange to be using that particular version; my local library has been using the ESR version (Extended Support Release) for almost as long as ESR has been around - Jan 2012 with ESR 10.