wicd

Allow "view only" client instances

Bug #395411 reported by Robby Workman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wicd
Triaged
Wishlist
Unassigned

Bug Description

Horrible summary, I know :/

Basically, denying a user complete access to wicd-client simply because he doesn't have permission to view/change certain things isn't really ideal.

Isolating privileged method calls from "normal" ones in such a way that any user could run the client, but privileged settings/changes/etcetera would be "grayed out" in the UI, is essentially what I'm after here. In other words, any user could run the client and see available networks, the current network, and so on, but only a user in "netdev" (or whatever) group would be able to connect/disconnect, view/change network auth info, etcetera.

Tags: 2.0 vpb-alpha
Adam Blackburn (adamblackburn)
Changed in wicd:
milestone: none → vpb-alpha
Adam Blackburn (adamblackburn)
Changed in wicd:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Andrew Psaltis (nacl) wrote :

Wouldn't this be something that PolicyKit would be good for? NM's settings dialog has a large chunk of it grayed out before it gets "unlocked" by the administrator password.

Scripts could also be controlled in a similar way, and not require launching a new process.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.