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

Access to about:debugging while blocking all extensions via GPO

  • 3 wótegrona
  • 1 ma toś ten problem
  • 1 naglěd
  • Slědne wótegrono wót Dom Langella

more options

Hello,

As the title mentions, applying a block to all extensions via "*" by utilizing Extension Management GPO will block about:debugging.

Is there a way to simultaneously have all extensions blocked and about:debugging available?

Here's the JSON - { "*": { "installation_mode": "blocked" } }


Appreciate your time and help, - Dom

Hello, As the title mentions, applying a block to all extensions via "*" by utilizing Extension Management GPO will block about:debugging. Is there a way to simultaneously have all extensions blocked and about:debugging available? Here's the JSON - { "*": { "installation_mode": "blocked" } } Appreciate your time and help, - Dom

Wšykne wótegrona (3)

more options

The reason we block about:debugging is because a user can explicitly load an addon on the about:debugging.

You're right, though, that this is probably a little heavy handed. Maybe I should just disable the "load temporary addon" button.

more options

Wubrane rozwězanje

more options

Thanks for the insight and feedback!