5 ms·
Not sure expiration is the worst problem with passwords. In no particular order, * Most are easy to remember (most of us don't use LastPass etc) * They authen
by JoeAltmaier 7y ago
Not sure expiration is the worst problem with passwords. In no particular order,
* Most are easy to remember (most of us don't use LastPass etc)
* They authenticate the user but not the service!
* They're leaky (the system tells you when you have the wrong one, facilitating several kinds of attacks)
* People leave them lying around all the time
* Changing one almost always involves using the old one (instead of starting over from first principles)
Don't get me started on usernames! If you have a large hashed password, then the username becomes irrelevant (except as a way of leaking information).
Here's a modest proposal:
* Insist on large hashed passwords (256bit or better).
* Forget about usernames. The password becomes an 'account key' and is all you need
* Allow delegation: from one account to another; enable/disable features even for the 'main' account; give away authority for delegation at the feature level
* Never deny login for any reason, because that leaks security info (e.g. 'that password is illegal' is information). Just trust every legal password, and if it doesn't exist in the system then create a new default account
- npongratz 7y ago> * Forget about usernames. The password becomes an 'account key' and is all you need When talking about your account, then -- such as when talking to Support -- how would you refer to your account? Would you be assigned an ID by the system, which you then have to save or remember? Not saying it's good or bad or anything, just want to understand the expected user experience.
- JoeAltmaier 7y agoAny amount of profile information can be associated with an account. But a better, more secure technique than describing the account, would be to create a temporary token for the account and share it with support. That proves you're authorized to ask support to make changes in that account.