In anon-base-files, there’s an anonymous /var/lib/dbus/machine-id which is meant to be shared across multiple anonymity focused distros. It doesn’t have a /etc/machine-id though.
Is there any reason not to anonymize this as well?
If not, it should be the same as /var/lib/dbus/machine-id.
Setting up anon-base-files (3:3.6-1) ...
Configuration file '/etc/machine-id'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** machine-id (Y/I/N/O/D/Z) [default=N] ?
Can we avoid this interactive dpkg conflict resolution dialog? Somehow preseed saying yes?
Anonimizar Machine-id solo es una parte , los ataques que rompen a la red tor buscan algo mas concreto que pueda ser utilizado en el forence como su numero unico de ID / Software IDs Attack / SIA
/proc/sys/kernel/random/boot_id
Welcome to the Whonix community ¡Bienvenido a la comunidad de Whonix!
Used Google translate but not sure of the accuracy. Usé el traductor de Google pero no estoy seguro de la exactitud.
Anonymize Machine-id is only a part, the attacks that break the network are looking for something more concrete that can be used in the forence as your unique ID / Software IDs Attack / SIA number
/ proc / sys / kernel / random / boot_id
With systemd 250 introducing an overriding machinei-id option, I don’t know if this needs to be revisited or perhaps this option provides an eaesier way to handle this?
Introducing KERNEL_INSTALL_MACHINE_ID= support within /etc/machine-info. This value will be preferred over any /etc/machine-id value.