News for hackers. Stuff that matters.
Re:Creative usernames and Spotify account hijacking by brown9-2 on Tuesday June 18, 2013 @10:51PM (#5903470)
Sounds like they are using the username as the key in their DBs, which sounds like the ultimate case of any pain:

Could the method for computing canonical usernames based on nodeprep.prepare() be salvaged? If not we would be in trouble since we use canonical usernames in various databases so that changing how to derive them in a non-backwards compatible way would be quite costly.

Re:Creative usernames and Spotify account hijacking by tantalor on Wednesday June 19, 2013 @12:52AM (#5903794)
Not necessarily. It their canonicalization function were idempotent (e.g., the identity), then this database scheme would work well.

How else do you map username to user id?

Re:Creative usernames and Spotify account hijacking by brown9-2 on Wednesday June 19, 2013 @10:54AM (#5905866)
Well generally it makes sense to use that userid as a primary key everywhere rather than the username. You only need the mapping of username to userid in one place. Their current scheme also makes it sound hard to change your username.
Re:Creative usernames and Spotify account hijacking by tantalor on Wednesday June 19, 2013 @12:10PM (#5906380)
Ah I fully agree. I misunderstood your post to say you should never use a user name as a key.