Thomas Haller 9b295f0df5 dhcp: make connection.mud-url configurable as global connection default ... Conceptionally, the MUD URL really depends on the device, and not so much the connection profile. That is, when you have a specific IoT device, then this device probably should use the same MUD URL for all profiles (at least by default). We already have a mechanism for that: global connection defaults. Use that. This allows a vendor drop pre-install a file "/usr/lib/NetworkManager/conf.d/10-mud-url.conf" with [connection-10-mud-url] connection.mud-url=https://example.com Note that we introduce the special "connection.mud-url" value "none", to indicate not to use a MUD URL (but also not to consult the global connection default).		2020-04-28 13:01:18 +02:00
..
nm-auth-subject.c	license: relicense "shared/nm-libnm-core-intern-aux/nm-auth-subject.[hc]" under LGPL-2.1+	2020-02-16 15:41:44 +01:00
nm-auth-subject.h	license: relicense "shared/nm-libnm-core-intern-aux/nm-auth-subject.[hc]" under LGPL-2.1+	2020-02-16 15:41:44 +01:00
nm-common-macros.h	dhcp: make connection.mud-url configurable as global connection default	2020-04-28 13:01:18 +02:00
nm-ethtool-utils.c	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
nm-ethtool-utils.h	shared: expose size of nm_ethtool_data array in header	2020-03-06 09:49:32 +01:00
nm-libnm-core-utils.c	shared: add nm_client_permission_result_to_string() helper	2019-12-10 07:53:25 +01:00
nm-libnm-core-utils.h	core: add and indicate NM_CAPABILITY_OVS capability on D-Bus	2019-12-21 11:33:59 +01:00