3 ms·
While this post might be trolling, I don't actually see many issues with this scheme. The weaknesses are that a password, once leaked, can't be changed. And
by londons_explore 7y ago
While this post might be trolling, I don't actually see many issues with this scheme.
The weaknesses are that a password, once leaked, can't be changed. And sending it over email pretty much constitutes a leak.
But on balance, password reuse is such a large problem that I suspect this scheme will end up with fewer account compromises per year than a service using regular password hashing without 2fa.
- viraptor 7y agoIt all depends on what the user can do now, and what can they do with the future releases. It's an accident waiting to happen. Maybe it will be ok. Every time I ran with scissors I've been ok.
- mindslight 7y agoWhat most sites call a "password" is really just a cached email challenge. Tweak this so it generates a new token on every challenge, and it's actually pretty slick. If the service is compromised such that the userdb is copied, they can just wipe the whole cache. The biggest sin here is inventing a new method, requiring actual analysis of its properties. The indignation from the cargo cult is a bonus though. Most of the upset is probably from people being prevented from setting their password to the same one they use on every other site.
- danShumway 7y agoMedium already got rid of passwords and uses email tokens for all logins. It's really annoying as an end user, but it does work. Assuming they're not a troll, I think their sin is trying to reinvent a method that already existed, and reinventing it poorly.
- vo2maxer 7y agoI’m not sure what to make of the “infosec” company on the post. Are they trolling as a marketing ploy? Are they ahead of the curve in password management? Is it a philosophical statement on the state of security in the world at large? Do we laugh? Do we cry? Do we shrug? Do we give up in disgust? Are they that incompetent? Rarely have I had so many mixed feelings ;-) This is how I came upon the Twitter thread: https://twitter.com/jeremyphoward/status/1203167252691898368 https://twitter.com/jeremyphoward/status/1203167252691898368
- danShumway 7y agoThey're conflating a lot of things that don't need to be conflated. You can generate a password for the user locally, when they create an account. You should still be hashing that password, not storing it in plain text. You should still give the user an automated option to generate a new password. You can still avoid sending the password over email, since that's almost guaranteed to be sent unencrypted over an open wire at some point. The beauty of this Twitter thread is that it starts out with an idea that makes some very mild sense, and then immediately descends into madness for no reason. I absolutely love that they consider a password personally identifying information, but are fine collecting emails because, "the user could use an anonymous one if they wanted to."