News for hackers. Stuff that matters.
Re:PostgreSQL and UUID as Primary Key by mewpmewp2 on Saturday July 06, 2024 @12:29AM (#40888171)
But then by default you are leaking potentially business sensitive data with your id if you are using it as public facing, which is unsecure design by default.

I would rather have secure data by default and opt in to optimise when it is clear this info is fine to leak.

Re:PostgreSQL and UUID as Primary Key by sgarland on Saturday July 06, 2024 @09:13AM (#40890264)
See other reply; I don’t believe that exposing this is as big an issue as people think. But even with that, there’s also no reason to do so. Internal ID friendly to the DB and eternal, random ID that does get exposed is a common practice. Or use JWE/JWT, and never show either.
Re:PostgreSQL and UUID as Primary Key by mewpmewp2 on Saturday July 06, 2024 @04:12PM (#40892894)
I don't know. Is it not? I frequently check out of curiosity when I'm buying something the order numbers and similar things that might of interest, if I notice integers. I imagine if you become a public company that would be very sensitive information in terms of the company is doing, and there would be strong push to check for that data, to get an advantage in the stock market.

It doesn't seem right to me to expose with such ease how many sales you are doing. It's definitely not intentional to expose it.

Re:PostgreSQL and UUID as Primary Key by lazide on Saturday July 06, 2024 @09:54PM (#40894699)
Auto increment ID’s also leak information.

Random UUID’s shouldn’t, but will impact performance, which in most cases will have more concrete impact on the business.

There is no such thing as a free lunch.