News for hackers. Stuff that matters.
Re:Facebook probably has your phone number, even if you neve... by patrec on Wednesday November 02, 2022 @06:01AM (#33433456)
Hash functions are only incredibly difficult to invert when the input domain is large, which is not the case with phone numbers. Even if you use a password hashing function that takes 1s to run (and if you need to frequently compare the hash, that's on the high side), you could practically invert the hash of an individual phone number. For this use case making it relatively expensive to obtain a single number in the clear would probably be good enough though.
Re:Facebook probably has your phone number, even if you neve... by robertlagrant on Wednesday November 02, 2022 @06:35AM (#33433700)
Salting exists for this reason.
Re:Facebook probably has your phone number, even if you neve... by ShowalkKama on Wednesday November 02, 2022 @06:49AM (#33433784)
even with salting it'd be trivial
Re:Facebook probably has your phone number, even if you neve... by eps on Wednesday November 02, 2022 @06:57AM (#33433865)
And how exactly would salting fit into matching plaintext phone numbers against a large blacklist?
Re:Facebook probably has your phone number, even if you neve... by Vinnl on Wednesday November 02, 2022 @07:04AM (#33433909)
How would that work if someone re-uploads your phone number? If it's not hashed with the same salt, then that wouldn't be blocked?
Re:Facebook probably has your phone number, even if you neve... by robertlagrant on Wednesday November 02, 2022 @08:48AM (#33434854)
Well, quite :) I don't see how the thing is supposed to work, given that people get other people's phone numbers when they change number. The only way to actually fix it is to stop uploading a user's contacts to their servers in the first place.