Privacy vs information brought by some logs about hw-probe

[linuxhw]

blkid is not collected anymore
fdisk output is useful for debugging multi-OS issues on the computer
lsblk output is useful for debugging partitions issues on the computer
ifconfig is used to check operability of network cards and to get salted sha512 of mac in order to distinguish computers

In 1.5 I'll add an option to skip collecting of unwanted logs, so you'll be able to skip collecting fdisk or lsblk.

Thanks!

[ArchangeGabriel]

(They are other logs having such issues, I was just listing some)

[Celti]

There are similar privacy implications around systemd information:

Take systemd-analyze for an example, which exposes partition UUIDs and device-mapper labels. The systemctl logs reveal more of the same.

[linuxhw]

There are similar privacy implications around systemd information:

Take systemd-analyze for an example, which exposes partition UUIDs and device-mapper labels. The systemctl logs reveal more of the same.

Fixed on server. Need to do the same on client side.

Thank you!

[linuxhw]

There are similar privacy implications around systemd information:

Take systemd-analyze for an example, which exposes partition UUIDs and device-mapper labels. The systemctl logs reveal more of the same.

UUIDs do not reveal any private info: https://liquidat.wordpress.com/2013/03/13/uuids-and-linux-everything-you-ever-need-to-know/

[linuxhw]

There are similar privacy implications around systemd information:

Take systemd-analyze for an example, which exposes partition UUIDs and device-mapper labels. The systemctl logs reveal more of the same.

Client-side fix: 10b5116