Loosely based on nm-applet.conf, but there are few differences:
- it keeps .NetworkManagerInfo, not sure whether it's needed
- it allows at_console users to use .NetworkManagerSettings.Secrets interface
- no access for context="default" users (rely on deny now really used by default)
I played with it a bit on one test system with wired connection only. I can switch to DHCP config fine, but switch to static IP config has no effect. Also tried with the configuration that should be close to the default config prior to dbus 1.2.6, and static IP config does not work either. So not sure if this is actually a policy flaw... Can anyone give it a try on system with some configured wireless connection as well? Stefan, does this address your problem?
Created attachment 326289
Possible new policy file
Tries to follow some recommendation mentioned here: lists.freedeskt op.org/ archives/ dbus/2008- December/ 010717. html
http://
Loosely based on nm-applet.conf, but there are few differences: Info, not sure whether it's needed Settings. Secrets interface
- it keeps .NetworkManager
- it allows at_console users to use .NetworkManager
- no access for context="default" users (rely on deny now really used by default)
I played with it a bit on one test system with wired connection only. I can switch to DHCP config fine, but switch to static IP config has no effect. Also tried with the configuration that should be close to the default config prior to dbus 1.2.6, and static IP config does not work either. So not sure if this is actually a policy flaw... Can anyone give it a try on system with some configured wireless connection as well? Stefan, does this address your problem?