Why even let users set their own passwords?
devever.net
Why even let users set their own passwords?
1–10 of 392 posts
Re: Why even let users set their own passwords?
#2Re: Why even let users set their own passwords?
#3Re: Why even let users set their own passwords?
#4...because it's easier and cheaper to apply one rule for every user and you're an outlier. Most users don't have password safes - they have passwords like 'Messi123' that they use across multiple sites, and therefore benefit from a second factor since their first factor is more or less non-existent.
Re: Why even let users set their own passwords?
#5In the tech wold we often forget that there is a wide disparity in people's ability to use tech. Take my father, there is no way he could use a password manager, or two factor, it's just never going to happen. He has a notebook of passwords, that's how he works and he won't change.
We cannot change everyones behaviour, no matter how much it would be better for them. That's a very well learnt lesson, over and over.
The world in 30 years time will be very different, the eldest generations will have grown up with passwords and the internet. Many will have been using password managers, 2 factor, other authentication systems and devices for much of their lives. It's going to be a slow, trickle down change, from "high tech" services down to everyday sites and systems.
Re: Why even let users set their own passwords?
#6Re: Why even let users set their own passwords?
#7How would a users use different devices?
Re: Why even let users set their own passwords?
#8Re: Why even let users set their own passwords?
#9Re: Why even let users set their own passwords?
#10The author's solution:
> Rather than allowing a user to set their own password, passwords can be issued in exactly the same way as API keys are now: a high-entropy password is randomly generated by the issuing website, and the user is shown the password once only and asked to record it. If the password is lost, a new password must be generated using the same process. The user cannot choose their password, but can get a new randomly generated one in the event of compromise. The password essentially becomes indistinguishable from an API key.