News for hackers. Stuff that matters.
Re:Prevent information leaking in Rails by swalberg on Wednesday October 28, 2015 @07:52PM (#10468279)
Hm, I thought it was going to be talking about leaking information from your app, not browser cache.

Putting the database row ID in urls, which is the Rails default, basically lets a competitor plot your growth with a simple script.

Re:Prevent information leaking in Rails by elithrar on Wednesday October 28, 2015 @08:19PM (#10468401)
> Putting the database row ID in urls, which is the Rails default, basically lets a competitor plot your growth with a simple script.

Which is only a 'problem' (we'll assume there's 1:1 between DB rows and growth) with incrementing column IDs. UUIDv4's or some other random ID (24-bit base64, composite IDs with a shard prefix, etc) don't have this problem.

Re:Prevent information leaking in Rails by rhizome on Wednesday October 28, 2015 @10:17PM (#10468811)
or slugs.