This is confusing, distracting and reducing productivity.
Here's a proposal:
indicator-appmenu gets, initially, read-only access to the root dbus (in order to draw the menu) and then asks for a password on the first menu call (by either mouse click or keyboard shortcut). All root privileges drop once the window is out of focus or closed.
This only requires that indicator-applet temporarily take elevated privileges. It would be important to drop privileges both for closing windows and windows loosing focus since a user application could take advantage of the raised privileges unless they were somehow isolated.
Having to enter a password is probably indication enough that an application has raised privileges.
If it were not, the root menu could be drawn with inversion of highlight (selected/mouseover) and unhighlighted (unselected/normal) colors.
This is confusing, distracting and reducing productivity.
Here's a proposal:
indicator-appmenu gets, initially, read-only access to the root dbus (in order to draw the menu) and then asks for a password on the first menu call (by either mouse click or keyboard shortcut). All root privileges drop once the window is out of focus or closed.
This only requires that indicator-applet temporarily take elevated privileges. It would be important to drop privileges both for closing windows and windows loosing focus since a user application could take advantage of the raised privileges unless they were somehow isolated.
Having to enter a password is probably indication enough that an application has raised privileges.
If it were not, the root menu could be drawn with inversion of highlight (selected/ mouseover) and unhighlighted (unselected/normal) colors.