Wicd UIs are typically run by non-root users.

However, the wicd daemon needs root privileges to run. Current wicd uses DBus policies, and requires the user running the UI to belong to a certain group (`netdev' currently) to be able to run the UI.

Running a non-root UI which sends DBus messages to a root daemon, which doesn't check where the message comes from, is a bit risky security-wise. See, for example, what happened when Wicd saved unsanitized input into the configfiles, and the daemon could be made run any binary as root.

polkit is a system letting use require the user input a password when root-level settings need to be changed. Imagine an "unlock button", which ungreys some inputs in the UI when the correct password is used. This obviously shouldn't be used to control per-user settings, but only system-wide (i.e. needing root privileges) settings.

Since Wicd is planned on targeting mainly laptops, is there a need to support dbus protocols older than dbus 0.80?

What about the possibility of using a db (ex. sqlite) to keep connection information instead of using text files for keeping track of connection information?

One idea that this might be useful for is keeping track of same essid on different ap's.

1. Since logging is setup only once when first started and typically not changed during server runtime, recommend that logging is setup on startup rather than creating a function that will be executed only once.
2. Since there is a --no-daemon mode, have script check for daemon (background) or foreground mode and have logging setup to go to file on daemon mode or to screen on no-daemon mode to assist in debugging while running.