dear Didier,

thanks for this quick C monitoring tool using the inotify API

I think this may be useful also for /etc/machine-id - which may be a
different ID from dbus I believe?

meanwhile an update on my adventures using chromium on Beowulf: it
basically stopped working since I overwrote my machine-id with
"d34dc0d3d34dc0d3d34dc0d3d34dc0d3" because, I believe, is not the
machine-id that chromium registered for the sessions of my profile /
users logged into Google.

I start then understanding at least why chromium reads this file: to
associate the device with the logged in profile. I believe this is
really nasty especially when other applications start accessing this
file and can track the ID across different programs, domains,
namespaces. For instance a google account can be traced by other
applications that are not from google itself.

I believe this is a violation of the GDPR at least in Europe and will
consult the good contacts I have among policy experts in the field.


ciao

-- 
  Denis "Jaromil" Roio      https://Dyne.org think &do tank
  Ph.D, CTO & co-founder    software to empower communities
  ✉ Haparandadam 7-A1, 1013AK Amsterdam, The Netherlands
  ✩ Profile and publications: https://jaromil.dyne.org
  𝄞 crypto κρυπτο крипто गुप्त् 加密 האנוסים المشفره
  ⚷ 6113D89C A825C5CE DD02C872 73B35DA5 4ACB7D10