Re:Ask HN: What does GDPR mean for banning users?
by thijsvandien on Tuesday May 01, 2018 @12:37PM
(#16968647)
To check for matches against that index, you'd still need to hash the email you're checking for with every distinct salt in your database, separately.
[ Parent
| on HN ]
Re:Ask HN: What does GDPR mean for banning users?
by 0xfaded on Tuesday May 01, 2018 @12:55PM
(#16968832)
Good point, if each email is individually salted as best practice for storing passwords they could not be indexed.
However, this would also mean that logging in using an email/username would also require a full scan.
More generally, if you want to uniquely salt your keys, you’re in trouble.
Re:Ask HN: What does GDPR mean for banning users?
by p49k on Wednesday May 02, 2018 @03:06PM
(#16980168)
> However, this would also mean that logging in using an email/username would also require a full scan
No it wouldn’t, and that’s what makes this specific case different. In your scenario, you can lookup the column you need by username or email, which is indexed. You can then retrieve the unique salt and password hash with no lookup penalty. This is not possible in the other case because there is no known column that can serve as the index.