4 ms·
> Back up a little bit. Start from the premise that you should never ever know the user's password. Period. Consider that a liability. This sounds reasonable u
by naasking 7y ago
> Back up a little bit. Start from the premise that you should never ever know the user's password. Period. Consider that a liability.
This sounds reasonable until you realize that requiring only the user to handle passwords creates an even bigger liability: users are terrible at creating, handling and remembering passwords. Giving them this sole responsibility means they create simple, short passwords and reuse them across multiple services, thus increasing their vulnerability.
Browsers that started handling passwords and helping users create good passwords was one of the greatest security UX improvements of the past 20 years IMO.
- 0xff00ffee 7y agoEverything you said is true, but completely unrelated. :) Here's why: we are talking about the huge legal difference between liability of the user and liability of the service. If user's pick poor passwords, that's their problem, and a problem with passwords in general. But if you store the password, suddenly you are opening yourself up to bigger risks, risks that could sink your product. Big difference.