News for hackers. Stuff that matters.
Re:Postgres sequences can skip 32 unexpectedly by jacobsenscott on Friday July 16, 2021 @10:57AM (#27856905)
I've certainly seen this be a problem - even if you and every future programmer who touches your code gets the authorization check right every time over the years the app is live, and over the hundreds or thousands of endpoints it exposes, plenty of apps don't get it right every time.

Using random id's is a nice and low effort additional layer of security there.

Re:Postgres sequences can skip 32 unexpectedly by worble on Friday July 16, 2021 @02:31PM (#27859547)
If you're not doing your authorization properly, then no, basic ID obfuscation is not an extra layer of security. If anything, the fact that some people might gloss over the glaring security issues because "well its random ids so I never decided to check" is worse, an incremental id can at least be easily tested while developing to make sure, or a nice white hat hacker might notice and let you know.
Re:Postgres sequences can skip 32 unexpectedly by tonyarkles on Friday July 16, 2021 @04:23PM (#27860808)
Depending, very much, on that balance between usability and security. For the use case in the story, I'd way rather talk about (and write down) incidents 122 through 124 with my team, rather than incidents 549697a9-dd6a-4a90-a5f4-b2ff1a1d9289, d6150929-a692-414b-ba9e-ccbcf5e48a59, and 2756998d-035f-42bc-a97d-4135529e85d9.