Thomas Haller ff816dec17 cloud-setup: require to explicitly opt-in for providers via environment variable ... "nm-cloud-setup" is supposed to work without configuration. However, it (obviously) fetches data from the network you are connected to (which might be untrusted or controlled by somebody malicious). The tool cannot protect you against that, also because the meta data services uses HTTP and not HTTPS. It means, you should run the tool only when it's suitable for your environment, that is: in the right cloud. Usually, the user/admin/distributor would know for which cloud the enable the tool. It's also wasteful to repeatedly probe for the unavailable cloud. So, instead disable all providers by default and require to opt-in by setting an environment variable. This can be conveniently done via `systemctl edit nm-cloud-provider.service` to set Environment=. Of course, a image can also pre-deploy such am override file.		2019-12-03 16:18:33 +01:00
..
cli	all: add device carrier flag	2019-11-22 10:18:27 +01:00
cloud-setup	cloud-setup: require to explicitly opt-in for providers via environment variable	2019-12-03 16:18:33 +01:00
common	libnm: add ipvx.dhcp-hostname-flags properties	2019-11-28 17:56:35 +01:00
tests	libnm: add ipvx.dhcp-hostname-flags properties	2019-11-28 17:56:35 +01:00
tui	all: unify format of our Copyright source code comments	2019-10-02 17:03:52 +02:00
meson.build	cloud-setup: add tool for automatic IP configuration in cloud	2019-11-28 19:52:18 +01:00
nm-online.c	all: manually drop code comments with file description	2019-10-01 07:50:52 +02:00