which would have been in v2.6.22-rc4 through the normal CVE process.We can but it will likely take a few weeks to get a good sampling. UUID is unique in the db so when someone checks in with the same UUID, the old one gets overwritten. I'll have to do regular copies of what the UUID holds over time. Smolt schedules a monthly check in which we literally just missed a few days ago.
The only other bits in there are wall time and utsname, so systems
with no CMOS clock would behave repeatably. Can we find out what
kernels are affected?
We seen a huge number of duplicates for certain values:
>From Mike McGrath (added to Cc)
Here's the top 5:
266 28caf2c3-9766-4fe1-9e4c-d6b0ba8a0132
336 810e7126-1c69-4aff-b8b1-9db0fa8aa15a
402 c8dbb9d3-a9bd-4ba6-b92e-4a294ba5a95f
884 06e84493-e024-44b1-9b32-32d78af04039
931 e2b67e1d-e325-4740-b938-795addb45280
The left number is times this month someone has submitted a profile with
that UUID. If we take the last one as an example has come from over 800
IP's in the last 20 days. It seems very unlikely that one person would
find his way to 800 different IP's this month. Let me know if you'd
like more.
Any other details would be interesting.