The location of machine-id is set to /etc/machine-id (systemd-ism), so
change it to what is expected on FreeBSD, /var/lib/dbus/machine-id.
Submitted by: Samy Mahmoudi <email@example.com>
jrm on Aug 17 2020, 4:15 PM.Authored by
Reading https://www.freedesktop.org/software/systemd/man/machine-id.html , it seems like we should either write /etc/machine-id directly, in place of or addition to the /var location; OR, symlink /etc/machine-id to the /var location. Patching software to look in a non-canonical location is going to be more error-prone than conforming.
The comment also reads:
Hashes are one-way functions. It's certainly true hashing is not always sufficient to make an input private; for example, very short keys like phone numbers or short passwords can be reversed by just brute-forcing the key space. Machineids are 128-bit uuids, though. Brute-forcing the entire 2^128 space is not feasible.
It seems like systemd adopted the dbus file and "promoted" it into /etc, if I'm reading the description right. So applications may look in both locations, depending on when they were written and against what OS. I guess I think we should write both, or symlink one to the other.
From the document that Conrad linked to, it sounds like Chromium is doing what is intended. What they are using the unique id for is another question.
It sounds like the link is intended to be from /etc/machine-id pointing to /var/lib/dbus/.