4 ms·
Most failed login attempts are probably the user's correct password with a letter or two transposed or missing. And a competent, ethical developer wouldn't stor
by michaelt 13y ago
Most failed login attempts are probably the user's correct password with a letter or two transposed or missing. And a competent, ethical developer wouldn't store the user's correct password except salted and hashed using an appropriate algorithm (like bcrypt).
Why would you store the one-character-off password with any less protection?
Given that one would only store incorrect login attempts in hashed form, I'm having trouble thinking of any useful analytics you could perform on them.
- refucktoring 13y agoOf course ethical devs would store like that. Ethics kinda goes out the window when, as a company, you get two choices: play ball with the local law or take your business out of the country. My point was that, due to human error, sometimes account credentials from one network end up in another network's login prompt. I do not find it improbable that a network like Facebook could br ordered to capture all invalid login attempts on certain "red-flagged" accounts, that would be pretty bad. A bit like subconsciously-volunteered phishing, but as the user you wouldn't think twice about it (and "burn" that other password from everywhere else you used it), no matter how paranoid you are.