Re:Twitter data breach exposes contact details for 5.4M acco...
by oarsinsync on Sunday July 24, 2022 @05:39AM
(#32211782)
> You can improve privacy by one-way transforming the number in a way your systems can't undo (eg hmac with a key in hsm configured for enc only, with rate limiting), but naively you lose agility and some useful capability (eg ban accounts with numbers from this range).
So store two hashes, one being the whole number, another being the number excluding the last 2 digits. These aren’t difficult problems to solve. The bigger issue is that they’re not revenue generating solutions, but rather the opposite.
Re:Twitter data breach exposes contact details for 5.4M acco...
by solarkraft on Sunday July 24, 2022 @12:57AM
(#32210456)
It's also something the service provider has to do and I can't verify as a user.
In a sense they are used as a kind of "hashcash" to raise the cost of fake accounts.
You can improve privacy by one-way transforming the number in a way your systems can't undo (eg hmac with a key in hsm configured for enc only, with rate limiting), but naively you lose agility and some useful capability (eg ban accounts with numbers from this range).