Re:Exploring PostgreSQL 18's new UUIDv7 support
by javawizard on Saturday October 18, 2025 @01:26AM
(#45625148)
Indeed, but one could easily argue that 128 bits of entropy aren't sufficient for a good invite token in the first place.
[ Parent
| on HN ]
Re:Exploring PostgreSQL 18's new UUIDv7 support
by pinkgolem on Saturday October 18, 2025 @01:45AM
(#45625222)
I am just puzzled why delifue calls something that, as far as I know is pretty standard across the industrie, bad practice
Re:Exploring PostgreSQL 18's new UUIDv7 support
by treve on Saturday October 18, 2025 @03:07AM
(#45625506)
There's 2 cases being discussed. A UUIDv7 is a bad secret, but it's fine for many other ids. If I can guess your user id, it shouldn't really matter because your business logic should prevent me from doing anything with that information. If I can guess your password reset token it's a different story because I don't need anything else beyond that token to do damage.
Re:Exploring PostgreSQL 18's new UUIDv7 support
by tracker1 on Monday October 20, 2025 @11:50AM
(#45645285)
But the random part of a UUIDv7 is 74 bits... larger than a 64-bit integer of random values. Larger than many systems use in total when generating random keys for such things. Likely a larger number of values than the total number of comments here on HN over a couple decades. It's emphatically NOT guessable.
Re:Exploring PostgreSQL 18's new UUIDv7 support
by treve on Tuesday October 21, 2025 @12:16AM
(#45652430)
[delayed]
Re:Exploring PostgreSQL 18's new UUIDv7 support
by nesarkvechnep on Saturday October 18, 2025 @02:41AM
(#45625418)
Because it is?