Funkcionalnosć toś togo sedła se pśez wótwardowańske źěła wobgranicujo, kótarež maju wašo dožywjenje pólěpšyś. Jolic nastawk waš problem njerozwězujo a cośo pšašanje stajiś, wobrośćo se na našo zgromoźeństwo pomocy, kótarež na to caka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomagaś.

Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

Is there information about using configurable security policies in Firefox 4?

  • 2 wótegronje
  • 3 maju toś ten problem
  • 45 naglědow
  • Slědne wótegrono wót Randy Davis

more options

I am trying to develop a package of Firefox 4.0 to roll out in my enterprise environment. I need to provide a way of locking down Firefox to roughly the same extent that Internet Explorer is locked down for our users. One of the security settings that I need to be able to set is a setting to turn off javascript for all outside domains, but have javascript work for any internal domain, ie *.internal_domain.com. Any help is appreciated.

I am trying to develop a package of Firefox 4.0 to roll out in my enterprise environment. I need to provide a way of locking down Firefox to roughly the same extent that Internet Explorer is locked down for our users. One of the security settings that I need to be able to set is a setting to turn off javascript for all outside domains, but have javascript work for any internal domain, ie *.internal_domain.com. Any help is appreciated.

Wšykne wótegrona (2)

more options
more options

Thank you for your response. I am currently using Mozilla.cfg successfully, but I have not been able to get the configurable security policies to work. Also, is it possible to use wildcards when specifying domain names in the capability.policy?