Ultimately, the problem is much bigger than /etc/machine-id since there are dozens of hardware IDs on any PC that can be used by malicious telemetry to silently to uniquely identify and track you, and the only solution to this problem currently is to make sure you really trust any software you use.
Systemd, in particular, acts a lot like malware for Linux because if you try to reset your machine-id a long list of stuff that breaks in in it. You could make a cron script to reset /etc/machine-id every day, but machine-id is so deep in the stack that you’d also have to reboot to ensure it’s updated.
I was unaware of this. As far as I can understand this is a design for admins who manage fleets and virtual machines, so it’s not surprising it comes from Lennart and systemd. However, even openbsd has /etc/machine-id. Over in bsd land it seems to come from dbus. Is the file a systemd design or a dbus design? Is it something users should be concerned about… probably, but all of computing is a nightmare. Just another fire to add to the fire pit.
Yeah, since OpenBSD doesn’t use systemd, that points to dbus origins for the file.