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

Understanding the best fix for a issue involving security.tls.version.fallback-limit in about:config

  • 1 பதிலளி
  • 0 இந்த பிரச்னைகள் உள்ளது
  • 8 views
  • Last reply by cor-el

Recently in our workplace, we had several computers that suddenly stopped being able to access several websites, the issue started shortly after pushing a updated Firefox across the floor.

I tracked the issue down to being related to security.tls.version.fallback-limit defaulting to 4, instead of the old 3.

Setting the value to 3 resolves the website accessibility issue.

A.) How can I confirm if this is a recent change or not? Everything I read seems to indicate the default should already be 3, but its very definitively not.

B.) What is the best way to push a pref adjustment change across the floor if the option isn't present in the registry and isn't a GPO option? Is my only option really to make some script that scans every computer's users folder, check every user folder's appdata\mozilla, scan every profile for a pref.js file, and do a string search for a reference line and then do a line addition if a certain string doesn't exist?

I can do this, it just doesn't seem like a good long term fix as I would have to run this script regularly as users come and go....

I am on FF 128.7.0esr (64-bit) under a new profile.

Recently in our workplace, we had several computers that suddenly stopped being able to access several websites, the issue started shortly after pushing a updated Firefox across the floor. I tracked the issue down to being related to security.tls.version.fallback-limit defaulting to 4, instead of the old 3. Setting the value to 3 resolves the website accessibility issue. A.) How can I confirm if this is a recent change or not? Everything I read seems to indicate the default should already be 3, but its very definitively not. B.) What is the best way to push a pref adjustment change across the floor if the option isn't present in the registry and isn't a GPO option? Is my only option really to make some script that scans every computer's users folder, check every user folder's appdata\mozilla, scan every profile for a pref.js file, and do a string search for a reference line and then do a line addition if a certain string doesn't exist? I ''can ''do this, it just doesn't seem like a good long term fix as I would have to run this script regularly as users come and go.... I am on FF 128.7.0esr (64-bit) under a new profile.
Attached screenshots

All Replies (1)

This fallback-limit pref has been there for quite some time (Firefox 62), so this is not a recent change. Some other change might be causing this problem if it started with a recent update. What security information shows "Tools -> Page Info -> Security" when this works?

You could use an autoconfig.cfg file to push pref changes to a profile if you can't do this via GPO or policies.json.

cor-el மூலமாக திருத்தப்பட்டது

Helpful?

கேள்வி எழுப்பு

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.