Any plans to make sure that Kick shares the same machine-id as Whonix post installation?
Mine was completely different after install. Just curious…
Any plans to make sure that Kick shares the same machine-id as Whonix post installation?
Mine was completely different after install. Just curious…
Machine ID sharing is an anonymity feature. Kicksecure intentionally does not include most anonymity-focused features, those are Whonix’s job. See:
Well could the argument be made for protection for VM users? Not everyone that uses Kick uses it baremetal, many use it in VM. Adopting it natively could extend these anti-correlation security benefits to Kicksecure VM hosts no?
How many applications actually use systemd’s sd_id128_get_machine_app_specific(). though?
Not relevant since NetworkManager is used instead but networkdconfd:
man networkd.conf.d (5): Global Network configuration files
DUIDType=
vendor
If “DUIDType=vendor”, then the DUID value will be generated using “43793” as the vendor identifier (systemd) and hashed contents of machine-id(5). This is the default if DUIDType= is not specified.
Also systemd-creds uses machine-id incorporated into the encryption key. So maybe security wise this could be an argument against it?
per-user encrypted credentials by poettering · Pull Request #30968 · systemd/systemd · GitHub