fdo-mirrors/NetworkManager
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git synced 2026-01-23 22:10:24 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
NetworkManager/src/org.freedesktop.NetworkManager.conf

152 lines
9.5 KiB
Text
Raw Normal View History

Initial revision git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@2 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-06-24 14:18:37 +00:00
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
2004-01-05 Colin Walters <walters@redhat.com> * named/named.conf: Add PID_FILE. * named/nm-named-manager.c: Always generate a pid file, since older BIND versions don't support "pid-file none". git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@359 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2005-01-05 20:40:38 +00:00
<policy user="root">
<allow own="org.freedesktop.NetworkManager"/>
<allow send_destination="org.freedesktop.NetworkManager"/>
2007-11-28 Tambet Ingo <tambet@gmail.com> Merge the beginnings of the new GSM card support. * src/ppp-manager/nm-ppp-manager.c (nm_ppp_manager_stop): Remove * the ppp watch source before killing pppd - If this happens from g_object_unref() then the ppp manager is already destroyed by the time the watch callback runs. * src/nm-hal-manager.c: Add a device_type_name string to the * device creators, so that we can print a nice human readable string when a device is added. * src/nm-umts-device.c (automatic_registration_get_network): * Query for the activated network, not much is done with the result thought. * src/nm-serial-device.c (nm_serial_device_get_reply): * Implement. (ppp_ip4_config): Change the device state to activated here for now. (real_check_connection): Make sure the connection includes ppp setting. * libnm-glib/nm-client.c (get_device): Handle umts devices. * libnm-glib/Makefile.am: Add the new files to build. * libnm-glib/nm-umts-device.c: * libnm-glib/nm-umts-device.h: Implement. 2007-11-26 Tambet Ingo <tambet@gmail.com> * src/nm-umts-device.c (automatic_registration_get_network): For * now, dial immediately, nm_serial_device_get_reply() isn't implemented correctly yet. * src/nm-serial-device.c (wait_for_reply_info_destroy): Don't * try to remove the timeout source - this function is only called when the timeout source has been removed. (nm_serial_device_wait_for_reply): Allocate the duplicate responses array to be big enough to contain the terminating zero element as well. The timeout argument is meant to be in seconds now. (real_deactivate_quickly): Implement. * src/NetworkManager.conf: Allow root to own "org.freedesktop.NetworkManager.PPP", deny it for everybody else. * libnm-util/nm-setting-umts.c: Network type and band properties * are ints, (not unsigned ints). * libnm-util/nm-setting-serial.c (nm_setting_serial_class_init): * Fix a small issue with parity bounds - capital letters have lower ascii codes than lower case letters. * libnm-util/nm-connection.c (register_default_settings): * Register serial and umts settings. 2007-11-22 Tambet Ingo <tambet@gmail.com> Remove the "index" property from devices as not all device types have this. * include/NetworkManager.h (NM_DBUS_PATH_DEVICE): Remove. * src/nm-hal-manager.c (nm_get_device_index_from_hal): Remove. (wired_device_creator): Get the device interface from hal to create the device. (wireless_device_creator): Ditto. * src/nm-device.c (nm_device_init): Remove the index member. (constructor): Remove the checks for index property, make interface property a require constructor property. Use the HAL udi for DBus path for devices. (nm_device_get_index): Remove. (set_property): Remove index handling. (get_property): Ditto. (nm_device_get_dbus_path): Remove. * src/nm-device-interface.c (nm_device_interface_init): Remove * the index property. * src/nm-device-802-3-ethernet.c * (nm_device_802_3_ethernet_link_activated): Access the device index through it's interface. (nm_device_802_3_ethernet_link_deactivated): Ditto. (nm_device_802_3_ethernet_new): Remove the useless argument test_dev. Remove index argument. Add interface argument. * src/nm-device-802-11-wireless.c * (nm_device_802_11_wireless_new): Remove the useless test_dev argument. Remove index argument. Add interface arugment. * src/NetworkManagerSystem.c * (nm_system_device_set_from_ip4_config): Get the device index through interface. (nm_system_set_mtu): Ditto. * introspection/nm-device.xml: Remove the "Index" property. 2007-11-21 Tambet Ingo <tambet@gmail.com> * src/nm-serial-device.c: * src/nm-serial-device.c: * src/nm-umts-device.c: * src/nm-umts-device.h: Implement. * src/nm-hal-manager.c (nm_get_device_driver_name): * libhal_free_string the string allocated by libhal. (modem_device_creator): Implement. (register_built_in_creators): Register the modem creator. * src/nm-device-802-11-wireless.c * (nm_device_802_11_wireless_new): Remove the unused test_dev argument. * src/nm-device-802-3-ethernet.c (nm_device_802_3_ethernet_new): * Ditto. * src/Makefile.am: Add new files to build. Link in ppp-manager. * libnm-util/nm-setting-umts.c: * libnm-util/nm-setting-umts.h: * libnm-util/nm-setting-serial.c: * libnm-util/nm-setting-serial.h: Implement. * libnm-util/Makefile.am: Add new files to build. git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@3116 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2007-11-29 14:38:07 +00:00
fix dbus conf file broken by 7c3063faea6f162fa3725abf98085bf8567219bd
2009-02-05 07:15:04 -05:00
<allow send_destination="org.freedesktop.NetworkManager"
ppp: don't require separate bus name for pppd plugin communication Not actually needed, and actually makes securing the daemon harder from a D-Bus perspective, since both bus names resolve to the same unique name anyway, and the unique name is what actually gets matched on inside dbus. Suggestion from Colin Walters.
2009-02-05 06:05:10 -05:00
send_interface="org.freedesktop.NetworkManager.PPP"/>
dbus: allow NetworkManager to talk to secret agents
2010-12-14 15:32:12 -06:00
<allow send_interface="org.freedesktop.NetworkManager.SecretAgent"/>
dbus: don't do <deny send_interface="..." /> in dbus service file It does more than intended; apart from denying messages to that particular interface it also denies all messages non-qualified with an interface globally. From the dbus-daemon manual: Be careful with send_interface/receive_interface, because the interface field in messages is optional. In particular, do NOT specify <deny send_interface="org.foo.Bar"/>! This will cause no-interface messages to be blocked for all services, which is almost certainly not what you intended. Always use rules of the form: <deny send_interface="org.foo.Bar" send_destination="org.foo.Service"/> We can just safely remove those rules, since we're sufficiently protected by the send_destination matches and method calls are disallowed by default anyway.
2015-10-23 12:03:40 +02:00
<!-- These are there because some broken policies do
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<deny send_interface="..." /> (see dbus-daemon(8) for details).
This seems to override that for the known VPN plugins.
dbus: ensure NM can talk to newly installed VPN plugins (fdo #39463) When new services are installed and the daemon reloads bus policy (like when installing new VPN plugins with rpm or dpkg) it appears the rules don't get loaded into NetworkManager's policy space. Thus any D-Bus message NM sends to the newly installed VPN plugin gets denied until a restart of NM or the machine. Work around this dbus bug by letting NM talk to all known VPN services in the NM policy file which will always exist when NM is around.
2011-08-19 16:55:16 -05:00
-->
<allow send_destination="org.freedesktop.NetworkManager.openconnect"/>
<allow send_destination="org.freedesktop.NetworkManager.openswan"/>
<allow send_destination="org.freedesktop.NetworkManager.openvpn"/>
<allow send_destination="org.freedesktop.NetworkManager.pptp"/>
<allow send_destination="org.freedesktop.NetworkManager.vpnc"/>
dbus: allow talking to the NetworkManager-SSH VPN plugin
2013-03-20 08:28:14 -05:00
<allow send_destination="org.freedesktop.NetworkManager.ssh"/>
dbus: allow communication with NetworkManager-iodine VPN plugin
2013-12-12 10:53:34 -06:00
<allow send_destination="org.freedesktop.NetworkManager.iodine"/>
dbus: allow talking to more plugins in DBus policy These two has been seen in the wild. Libreswan is the RHEL's openswan fork.
2015-08-27 15:09:58 +02:00
<allow send_destination="org.freedesktop.NetworkManager.l2tp"/>
<allow send_destination="org.freedesktop.NetworkManager.libreswan"/>
dbus: allow talking to fortisslvpn plugin
2015-10-06 17:31:50 +02:00
<allow send_destination="org.freedesktop.NetworkManager.fortisslvpn"/>
dbus: add strongswan to the vpn plugin bus names
2015-10-23 12:05:37 +02:00
<allow send_destination="org.freedesktop.NetworkManager.strongswan"/>
vpn: convert NMVpnConnection <-> VPN service communication to GDBus (bgo #745307) Of special note is the new D-Bus rule to allow root to talk to org.freedesktop.NetworkManager.VPN.Plugin, without which NetworkManager would not hear signals from the VPN plugins. Oddly, this worked fine with dbus-glib... https://bugzilla.gnome.org/show_bug.cgi?id=745307
2015-02-25 16:31:37 -06:00
<allow send_interface="org.freedesktop.NetworkManager.VPN.Plugin"/>
dns: use DBus to make dnsmasq nameserver changes Use DBus to make nameserver updates rather than restarting the dnsmasq binary again and again. Signed-off-by: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical.com> https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00144.html
2016-03-22 10:03:44 -04:00
dbus: allow firewalld to communicate with NetworkManager Usually, this "<allow send_destination="..."/>" part is shipped by firewalld's D-Bus policy. However, if firewalld is initially not installed with NetworkManager already running, dbus-daemon seems to cache the missing permission for the D-Bus connection. As a result, when installing and starting firewalld, NetworkManager requests fail until restart: firewall: [0x7f4b83643890,change:"eth1"]: complete: request failed (Rejected send message, 1 matched rules; type="method_call", sender=":1.3" (uid=0 pid=715 comm="/usr/sbin/NetworkManager --no-daemon ") interface="org.fedoraproject.FirewallD1.zone" member="changeZone" error name="(unset)" requested_reply="0" destination=":1.25" (uid=0 pid=1243 comm="/usr/bin/python -Es /usr/sbin/firewalld --nofork -")) https://bugzilla.redhat.com/show_bug.cgi?id=1436770 (cherry picked from commit cc1d409ba886e8e7c33f845790cfc700fcd2d854)
2017-04-21 11:56:28 +02:00
<allow send_destination="org.fedoraproject.FirewallD1"/>
dns: use DBus to make dnsmasq nameserver changes Use DBus to make nameserver updates rather than restarting the dnsmasq binary again and again. Signed-off-by: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical.com> https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00144.html
2016-03-22 10:03:44 -04:00
<!-- Allow the custom name for the dnsmasq instance spawned by NM
all: replace "it's" with "its" where needed
2018-04-18 14:13:28 +02:00
from the dns dnsmasq plugin to own its dbus name, and for
dns: use DBus to make dnsmasq nameserver changes Use DBus to make nameserver updates rather than restarting the dnsmasq binary again and again. Signed-off-by: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical.com> https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00144.html
2016-03-22 10:03:44 -04:00
messages to be sent to it.
-->
<allow own="org.freedesktop.NetworkManager.dnsmasq"/>
<allow send_destination="org.freedesktop.NetworkManager.dnsmasq"/>
2004-01-05 Colin Walters <walters@redhat.com> * named/named.conf: Add PID_FILE. * named/nm-named-manager.c: Always generate a pid file, since older BIND versions don't support "pid-file none". git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@359 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2005-01-05 20:40:38 +00:00
</policy>
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<policy context="default">
<deny own="org.freedesktop.NetworkManager"/>
dbus: final dbus policy fixes (bgo #563730) Keep explicit denials, consolidate stuff, ensure that when denying send_interface it's almost always matched with send_destination.
2009-02-17 10:43:53 -05:00
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<deny send_destination="org.freedesktop.NetworkManager"/>
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Basic D-Bus API stuff -->
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.DBus.Introspectable"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.DBus.Properties"/>
exported-object: add support for DBus ObjectManager interface NMExportedObject now derives from GDBusObjectSkeleton, which is what GDBusObjectManagerServer wants. The main GDBusConnection and each private server connection now gets a new GDBusObjectManagerServer, and exported objects are registered with that instead of individually exporting each GDBusInterfaceSkeleton. Previously exported objects were not referenced by the BusManager, but instead removed from the exports hash via weak references. The GDBusObjectManagerServer instead references exported objects, which can make them live much longer than they did before. Co-Authored-By: Thomas Haller <thaller@redhat.com>
2015-07-20 17:30:02 -05:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.DBus.ObjectManager"/>
dbus: fix issues with root being at_console When root is at_console, the at_console stuff overrides the user=root section. Since the default section will deny-by-default, explicitly allow certain D-Bus interfaces to be usable by at_console users (including root when root is at_console) prevents root from being denied access to those interfaces when root is at_console.
2009-05-10 00:20:12 -04:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Devices (read-only properties, no methods) -->
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
send_interface="org.freedesktop.NetworkManager.Device.Adsl"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
send_interface="org.freedesktop.NetworkManager.Device.Bond"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
send_interface="org.freedesktop.NetworkManager.Device.Bridge"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
send_interface="org.freedesktop.NetworkManager.Device.Bluetooth"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Wired"/>
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Generic"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Gre"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Infiniband"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Macvlan"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Modem"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.OlpcMesh"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Team"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Tun"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Veth"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Vlan"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.WiMax.Nsp"/>
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.AccessPoint"/>
core/devices: Add P2P Wifi device and peer tracking This only adds the new device type and simple peer list handling.
2018-10-10 23:30:46 +02:00
<allow send_destination="org.freedesktop.NetworkManager"
wifi-p2p: rename Wi-Fi P2P After renaming the files, also rename all the content to follow the "Wi-Fi P2P" naming scheme.
2019-01-28 15:21:59 +01:00
send_interface="org.freedesktop.NetworkManager.WifiP2PPeer"/>
dbus: fix issues with root being at_console When root is at_console, the at_console stuff overrides the user=root section. Since the default section will deny-by-default, explicitly allow certain D-Bus interfaces to be usable by at_console users (including root when root is at_console) prevents root from being denied access to those interfaces when root is at_console.
2009-05-10 00:20:12 -04:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Devices (read-only, no security required) -->
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
send_interface="org.freedesktop.NetworkManager.Device.WiMax"/>
dbus: fix issues with root being at_console When root is at_console, the at_console stuff overrides the user=root section. Since the default section will deny-by-default, explicitly allow certain D-Bus interfaces to be usable by at_console users (including root when root is at_console) prevents root from being denied access to those interfaces when root is at_console.
2009-05-10 00:20:12 -04:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Devices (read/write, secured with PolicyKit) -->
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device.Wireless"/>
core/devices: Add P2P Wifi device and peer tracking This only adds the new device type and simple peer list handling.
2018-10-10 23:30:46 +02:00
<allow send_destination="org.freedesktop.NetworkManager"
wifi-p2p: rename Wi-Fi P2P After renaming the files, also rename all the content to follow the "Wi-Fi P2P" naming scheme.
2019-01-28 15:21:59 +01:00
send_interface="org.freedesktop.NetworkManager.Device.WifiP2P"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Device"/>
dbus: fix issues with root being at_console When root is at_console, the at_console stuff overrides the user=root section. Since the default section will deny-by-default, explicitly allow certain D-Bus interfaces to be usable by at_console users (including root when root is at_console) prevents root from being denied access to those interfaces when root is at_console.
2009-05-10 00:20:12 -04:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Core stuff (read-only properties, no methods) -->
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Connection.Active"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.DHCP4Config"/>
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.DHCP6Config"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.IP4Config"/>
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.IP6Config"/>
dbus: fix formatting of dbus permissions file
2009-07-28 10:07:52 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.VPN.Connection"/>
dbus: ensure only root can change debug levels
2010-05-04 12:07:57 -07:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Core stuff (read/write, secured with PolicyKit) -->
dbus: allow NetworkManager to talk to secret agents
2010-12-14 15:32:12 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
send_interface="org.freedesktop.NetworkManager"/>
DBus: merge NetworkManger{,SystemSettings} Remove the org.freedesktop.NetworkManagerSystemSettings bus name and have everybody talk to org.freedesktop.NetworkManager. Now that we have a single settings service that's embedded in the main daemon, we don't need separate names anymore.
2010-08-06 21:21:24 -04:00
<allow send_destination="org.freedesktop.NetworkManager"
NetworkMangerSettings -> NetworkManager.Settings Just for consistency, make settings related stuff live under the org.freedesktop.NetworkManager namespace, rather than its own org.freedesktop.NetworkManagerSettings namespace. Renames are done for DBus interface names, DBus object paths, and polkit actions.
2010-08-07 01:07:44 -04:00
send_interface="org.freedesktop.NetworkManager.Settings"/>
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Settings.Connection"/>
DBus: merge NetworkManger{,SystemSettings} Remove the org.freedesktop.NetworkManagerSystemSettings bus name and have everybody talk to org.freedesktop.NetworkManager. Now that we have a single settings service that's embedded in the main daemon, we don't need separate names anymore.
2010-08-06 21:21:24 -04:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Agents; secured with PolicyKit. Any process can talk to
the AgentManager API, but only NetworkManager can talk
to the agents themselves. -->
dbus: allow NetworkManager to talk to secret agents
2010-12-14 15:32:12 -06:00
<allow send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.AgentManager"/>
dbus: kill at_console usage in permissions (bgo #707983) (rh #979416) at_console permissions as implemented by D-Bus have some problems: 1) it is now fully redundant with PolicyKit and session tracking via systemd/ConsoleKit 2) it uses a different mechanism than PolicyKit or systemd to determine sessions and whether the user is on local or not (pam_console) 3) it was never widely implemented across so removing it harmonizes D-Bus permissions on all supported distros To that end, remove the at_console section of the D-Bus permissions, and rely on session-tracking and PolicyKit to ensure operations are locked down. No changes are being made to PolicyKit or session-tracking, so any operations denied by those mechanisms are still denied, and no permissions are being relaxed. Instead, this should allow remote users who log in via remote desktop or SSH to inspect network state, change connection parameters, and start/stop interfaces. Obviously if you are remote, you should not touch the interface which your connection is using, but that concern shouldn't prevent all the other nice stuff that you can do with NM. https://bugzilla.gnome.org/show_bug.cgi?id=707983 https://bugzilla.redhat.com/show_bug.cgi?id=979416
2014-01-09 12:10:31 -06:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<!-- Root-only functions -->
dbus: don't do <deny send_interface="..." /> in dbus service file It does more than intended; apart from denying messages to that particular interface it also denies all messages non-qualified with an interface globally. This blocks messages completely unrelated to wpa_supplicant, such as NetworkManager communication with the VPN plugins. From the dbus-daemon manual: Be careful with send_interface/receive_interface, because the interface field in messages is optional. In particular, do NOT specify <deny send_interface="org.foo.Bar"/>! This will cause no-interface messages to be blocked for all services, which is almost certainly not what you intended. Always use rules of the form: <deny send_interface="org.foo.Bar" send_destination="org.foo.Service"/> We can just safely remove those rules, since we're sufficiently protected by the send_destination matches and method calls are disallowed by default anyway. https://bugzilla.gnome.org/show_bug.cgi?id=763880
2016-03-20 12:06:42 +01:00
<deny send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager"
send_member="SetLogging"/>
<deny send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager"
send_member="Sleep"/>
<deny send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Settings"
send_member="LoadConnections"/>
<deny send_destination="org.freedesktop.NetworkManager"
send_interface="org.freedesktop.NetworkManager.Settings"
send_member="ReloadConnections"/>
dns: use DBus to make dnsmasq nameserver changes Use DBus to make nameserver updates rather than restarting the dnsmasq binary again and again. Signed-off-by: Mathieu Trudel-Lapierre <mathieu.trudel-lapierre@canonical.com> https://mail.gnome.org/archives/networkmanager-list/2016-March/msg00144.html
2016-03-22 10:03:44 -04:00
<deny own="org.freedesktop.NetworkManager.dnsmasq"/>
<deny send_destination="org.freedesktop.NetworkManager.dnsmasq"/>
2004-01-05 Colin Walters <walters@redhat.com> * named/named.conf: Add PID_FILE. * named/nm-named-manager.c: Always generate a pid file, since older BIND versions don't support "pid-file none". git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@359 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2005-01-05 20:40:38 +00:00
</policy>
dbus: increase 'max_replies_per_connection' limit in D-Bus configuration D-Bus default limit of replies per connection has been lowered to 128 due to CVE-2014-3638, see: http://cgit.freedesktop.org/dbus/dbus/commit/?id=5bc7f9519ebc6117ba300c704794b36b87c2194b https://bugs.freedesktop.org/show_bug.cgi?id=81053 The limit seems to be too low and causes problems in libnm-glib, that will not return all NetworkManager connection profiles if there are too many of them (roughly more than the limit). As a consequence, libnm-glib based clients will not work properly. Lets increase the limit in our D-Bus org.freedesktop.NetworkManager.conf configuration as we had it before. See also older commit d5b31d55fa1536a5bd08cf85929ac63a8f723467 that did the opposite thing (removing the limit because the default D-Bus limit was 8192 at that time).
2015-05-21 12:25:45 +02:00
org.freedesktop.NetworkManager.conf: don't use tabs (cherry picked from commit 8583e62276a23a7ea858edf6c71d122e22f41955)
2017-04-21 11:42:45 +02:00
<limit name="max_replies_per_connection">1024</limit>
<limit name="max_match_rules_per_connection">2048</limit>
Initial revision git-svn-id: http://svn-archive.gnome.org/svn/NetworkManager/trunk@2 4912f4e0-d625-0410-9fb7-b9a5a253dbdc
2004-06-24 14:18:37 +00:00
</busconfig>
Reference in a new issue Copy permalink