On Mon, 7 Jan 2019 at 15:19, Lennart Poettering <mzerqung@xxxxxxxxxxx> wrote: > > On Mo, 07.01.19 13:32, Stephen John Smoogen (smooge@xxxxxxxxx) wrote: > > > On Mon, 7 Jan 2019 at 12:32, John Harris <johnmh@xxxxxxxxxxxxx> wrote: > > > > > > On Monday, January 7, 2019 11:34:47 AM EST Ben Cotton wrote: > > > > The Fedora community cares about privacy and is adverse to tracking > > > > measures. We don't want to track; just count. > > > > > > If this is ever implemented, we should probably notify end users and provide > > > an easy way to disable this. If you pass an identifier, that enables client > > > tracking. > > > > The original proposla was looking at something to what yum has had > > built into it for a while. Every yum installation has a file > > /var/lib/yum/uuid which contains whatever was pulled from > > /proc/sys/kernel/random/uuid when yum was installed. Here is one > > example 34cb9496-a62c-496e-8935-22f550247262 > > Uh, please don't do it this way. People build reusable images of As I said that was the original proposal which was from a proof of concept of what was already in existence. It has a bunch of problems as you said. The reason for using the /proc/sys was because it could be cron'd and rebuilt regularly if needed and the kernel items was avaliable for EL5 (when I started working on this) -> EL7. With systemd's /etc/machine-id and having a regular hmac regeneration process would be equally useful. > Fedora that are then run unmodified in many instances. If you invent a > new file for a new uuid like this then it's highly unlikely people > will reset it when building such images, and hence your counting will > count all such instances as one, which you probably don't want. > > Hence, any such uuid should be keyed off /etc/machine-id, as that file > exists for purposes like this, and the chance that it is reset during > image building is higher, and doesn't require people to reset uuids > all over the place. > > hence my recommendation to derive the any uuid for purposes like this > from /etc/machine-id, by using a HMAC of some kind (see other mail). > > Lennart > > -- > Lennart Poettering, Red Hat > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
