News for hackers. Stuff that matters.
Re:We are sorry by r00fus on Wednesday February 08, 2012 @03:37PM (#3568359)
However, phonenumber+userid creates lots of nice unique hashes.

If they are going to hash the data, they should salt it (and possibly use key strengthening a la bcrypt, etc).

Re:We are sorry by lazerwalker on Wednesday February 08, 2012 @04:01PM (#3568448)
Hashing phonenumber+userid does absolutely nothing for them, though.

The purpose of uploading your contacts is so that if Jack's phone number is (555) 555-5555, and Sam uploads a contact list saying that he is friends with a guy whose phone number is (555) 555-5555, Path can match up those two phone numbers (or hashed versions of them) and tell Sam that Jack is a member. That match-up doesn't work if the phone number is stored as (a hashed version of) 5555555555jack and 5555555555sam.

Re:We are sorry by maxerickson on Wednesday February 08, 2012 @04:09PM (#3568481)
They could take the phone numbers, sort them and hash them together. So if Sam is 5 and Jack is 6, they both upload the hashed social relationship 56 to the system and it can match them up.

It wouldn't keep someone with access from checking if a social relationship existed in the database, but it should make recovering phone numbers and the like from the hashes quite a lot harder.

Re:We are sorry by harryh on Wednesday February 08, 2012 @04:25PM (#3568556)
That only works though if you have both Jack & Sam's phone books (and they have each other in their books) so the hit rate would go down, possibly significantly.
Re:We are sorry by harryh on Wednesday February 08, 2012 @04:05PM (#3568462)
But if you do this then you can't match phone #s in a users phone book against phone numbers in your database.