Thomas Haller d1a94a85b1 device: hash a per-host key for ipv4.dhcp-client-id=stable ... Otherwise, the generated client-id depends purely on the profile's stable-id. It means, the same profile (that is, either the same UUID or same stable-id) on different hosts will result in identical client-ids. That is clearly not desired. Hash a per-host secret-key as well. Note, that we don't hash the interface name. So, activating the profile on different interfaces, will still yield the same client-id. But also note, that commonly a profile is restricted to one device, via "connection.interface-name". Note that this is a change in behavior. However, "ipv4.dhcp-client-id=stable" was only added recently and not yet released. Fixes: 62a7863979		2018-05-28 14:58:24 +02:00
..
cli	cli: avoid bogus line seprator in pretty-output	2018-05-25 17:36:47 +02:00
common	device: hash a per-host key for ipv4.dhcp-client-id=stable	2018-05-28 14:58:24 +02:00
tests	cli: fix property matching	2018-05-28 11:33:40 +02:00
tui	all: use the elvis operator wherever possible	2018-05-10 14:36:58 +02:00
meson.build	build/meson: use variables for ldflags and linker-script	2018-01-11 12:46:01 +01:00
nm-online.c	all: require glib 2.40	2018-01-18 11:45:36 +01:00