11.3. Locking Down Enabled Extensions
org.gnome.shell.development-toolskey ensures that the user cannot use GNOME Shell's integrated debugger and inspector tool (Looking Glass) to disable any mandatory extensions.
Procedure 11.3. Locking down enabled extensions
- Create a
localdatabase file for machine-wide settings in
[org/gnome/shell] # List all extensions that you want to have enabled for all users enabled-extensions=['firstname.lastname@example.org', 'email@example.com'] # Disable access to Looking Glass development-tools=falseThe
enabled-extensionskey specifies the enabled extensions using the extensions' uuid (firstname.lastname@example.org and email@example.com).The
development-toolskey is set to false to disable access to Looking Glass.
- Override the user's setting and prevent the user from changing it in
# Lock the list of mandatory extensions and access to Looking Glass /org/gnome/shell/enabled-extensions /org/gnome/shell/development-tools
- Update the system databases:
- Users must log out and back in again before the system-wide settings take effect.
org.gnome.shell.development-toolskeys, any extensions installed in
/usr/share/gnome-shell/extensionsthat are not listed in the
org.gnome.shell.enabled-extensionskey will not be loaded by GNOME Shell, thus preventing the user from using them.