3 ms·
UUIDs leak information, by definition. For that reason, I'm not a fan. It's just leaking on the other side. I'll explain: A UUID should be pretty unique in the
by zhte415 4y ago
UUIDs leak information, by definition. For that reason, I'm not a fan. It's just leaking on the other side.
I'll explain: A UUID should be pretty unique in the universe. Wherever it crops up, as there should always be an assumption of the possibility of leaking data and associated data at the same time, whomever the UUID belongs to has had their information leaked. That could be associated meta data in a request like IP address, to a print out that has a user's UUID in the header. In all cases it ties data to an individual.
Better is to just use a high integer that doesn't simply increment, but changes by an amount. But low enough to blur into noise. Heck, this can be rotated.
I stand to be convinced otherwise, but via the reasoning above I believe UUIDs are not desirable for user privacy.
- adamckay 4y agoI don't understand what you mean here. You're saying that because UUIDs can be assumed to be unique in the universe, when it's leaked alongside other data it can then be correlated with other data leaks to tie data to an individual? How does a user ID being `8646846` make it any safer from leaks or correlation than `123e4567-e89b-12d3-a456-426614174000`?