Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Why is config tls.version.enable-deprecated not in ADMX template

  • 3 amsoshi
  • 0 sa na da wannan matsala
  • 1 view
  • Amsa ta ƙarshe daga Mike Kaply

jasonabeckett
jasonabeckett
more options

Why is the config option security.tls.version.enable-deprecated not defined in the latest (4.7) ADMX template?

Why is the config option security.tls.version.enable-deprecated not defined in the latest (4.7) ADMX template?

All Replies (3)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

I see this pref mentioned here:

jasonabeckett
jasonabeckett Mai mallakar tambaya
more options

Interesting. I wonder why when imported into MEM, it is not available:

Mike Kaply
Mike Kaply
  • Moderator
more options

That list is a list of the security preferences supported by the new JSON Preferences policy.

What's you're seeing in MEM is the old method of setting preferences (where the names were explicitly in the ADMX). Support for that preference was added after we deprecated the old preference policy.

See:

https://github.com/mozilla/policy-templates/blob/master/README.md#preferences