Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Access to about:debugging while blocking all extensions via GPO

  • 3 Mbohovái
  • 1 oguereko ko apañuái
  • 64 Hecha
  • Mbohovái ipaháva 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

Opaite Mbohovái (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

Ñemoĩporã poravopyre

more options

Thanks for the insight and feedback!