News for hackers. Stuff that matters.
Re:PostgreSQL and UUID as Primary Key by groestl on Saturday July 06, 2024 @10:01AM (#40890531)
> Using completely random UUIDs is IMO the worst choice

Can't say that without context. I've worked in systems where even the version bits were randomized, and for good reason (i know, technically, no UUID anymore).

Re:PostgreSQL and UUID as Primary Key by stouset on Saturday July 06, 2024 @10:33AM (#40890677)
I’m talking about default choices. UUIDv7 has few significant downsides for most cases. UUIDv4 has serious downsides. There are obviously cases where the latter is appropriate but that will come from unique requirements.
Re:PostgreSQL and UUID as Primary Key by groestl on Saturday July 06, 2024 @10:55AM (#40890794)
How about secure by default?
Re:PostgreSQL and UUID as Primary Key by stouset on Sunday July 07, 2024 @04:41PM (#40900312)
“Secure” is only meaningful against a defined threat model.

Most threat models for database IDs do not require their creation timestamp to be secret. Meanwhile every use case for database IDs requires them to be looked up in an index.

Re:PostgreSQL and UUID as Primary Key by groestl on Wednesday July 10, 2024 @04:05AM (#40924693)
I've run multiple info-exfiltrating attacks based on timestamps and sequential identifiers against various actors. There you have your threat model. While I don't have any clue about your "most", I suggest you don't ignore this vector for your opsec.