Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

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

Echekwara usoro a. Biko jụọ ajụjụ ọhụrụ ma ọ bụrụ na ị chọrọ enyemaka.

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

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 Jụọ onye nwe ya ajụjụ
more options

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

Mike Kaply
Mike Kaply
  • Top 25 Contributor
  • 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