You might not need to store plaintext email addresses

Re:You might not need to store plaintext email addresses by webmobdev on Monday November 02, 2020 @04:16AM (#24966080)

It's a good idea to protect user privacy. One drawback I can think of storing a hashed email is - What if the user forgets the username / email id and wants to know it? (This is a common use case). In such a case you have to collect additional unique data to help the user gain access to their account, but that defeats the original purpose - to protect user privacy.

[ Parent | on HN ]

Re:You might not need to store plaintext email addresses by opk on Monday November 02, 2020 @04:31AM (#24966173)

People often forget usernames but not so often e-mails. The e-mail is usually the primary/only means of identifying users anyway so you're not going to provide it back on request anyway.

[ Parent | on HN ]

Re:You might not need to store plaintext email addresses by Hitton on Monday November 02, 2020 @05:39AM (#24966573)

They won't forget the email, but they might easily forget with which email they registered (happened to me).

[ Parent | on HN ]

Re:You might not need to store plaintext email addresses by trengorilla on Monday November 02, 2020 @06:52AM (#24967068)

How many e-mails could you possibly have that makes trial and error not a good solution in this scenario?

[ Parent | on HN ]

Re:You might not need to store plaintext email addresses by danaris on Monday November 02, 2020 @12:38PM (#24970738)

Well, first of all, I have 5 email accounts that I regularly use.

One of those uses multiple domains (it's an iCloud account that I registered way back in the iTools days, so it supports @mac.com, @me.com, and @icloud.com....possibly even @itools.com, not sure about that one).

I regularly use a + extension to the addresses that support it when I'm signing up somewhere that I don't 100% trust, and that allows arbitrary additions to the address. And I don't always remember what version of a site's name I will have used (eg, [email protected], [email protected], [email protected], etc).

I recognize that I'm an outlier, but trial and error is completely infeasible in this scenario.

[ Parent | on HN ]

Re:You might not need to store plaintext email addresses by kd913 on Monday November 02, 2020 @08:52AM (#24968104)

I tend to use aliases so I can filter/discover which exact service is perhaps selling my email.

ie <email prefix>+<tag>@gmail.com

That tag could be anything or everything.

[ Parent | on HN ]

Re:You might not need to store plaintext email addresses by hardwaresofton on Monday November 02, 2020 @04:23AM (#24966126)

You could use a combination of TOTP/google/facebook or some other side channel verification and use that to allow unlimited tries for a certain period of time to allow for more guesses? I'm thinking that for the most part people generally have/keep <5 email addresses (that they use often enough to log in with) so they should be able to just iterate through the list of emails that they've used over their lifetime and figure it out?

I do wonder though -- if the hash secret gets out then I think we're right back to where we started... it would be easy to cross-reference leaded email DBs with the dumped DB and work backwards. I'm now a bit less sure this does much for use privacy against an even slightly motivated opponent (one who would almost certainly have access to at least one dump of previously-exposed emails)...

[ Parent | on HN ]