Because you don't want your sysadmin logging into your favorite dating site as you? If you are going to do this right, you need email encryption. In which case, you have a client-side certificate. In which case, you might as well just authenticate over SSL with that certificate. But hey, why do something secure and built-in to every browser (even IE) when you can invent your own protocol instead? It's the Internet! A…
Well, the sysadmin could click on "restore password" on that super-secret site they want to steal your password to, and then check your mailbox. So this is really no different in terms of security. Also, I'm sure I have a dozen restore password emails in GMail somewhere. And I'm sure I'm not alone.
Ask HN: Why not log into web sites via email without any password?
31–40 of 40 posts
Re: Ask HN: Why not log into web sites via email without any password?
#32For the unaware, the app basically plugs in to your browser and with a "master password" recalls all your logins. I basically go to a webpage, hit the 1p button and I'm golden. If it's the start of a session, I'm asked to enter my master password and that's about it.
Obviously the service doesn't have any control of this, and I am reliant on 1password's security and the security of my password, but it's convenient. I can't see email being the only login because I'd be worried of giving my email password to anybody.
Re: Ask HN: Why not log into web sites via email without any password?
#33If you take this idea and strip out the silly email part, you have the core idea behind OpenID.
The difference between this idea and OpenID is that real people actually know their email address, but not "that thing with all the squigglies in it, you know, the email address for Google". I really, really wish the OpenID standard had used email addresses as the identifier.
With a URL it's trivial. Take mine for instance - andrewducker.livejournal.com
1) Go to that URL. Look for something like this: http://www.livejournal.com/openid/server.bml />
2) Forward the user there, saying that you're expecting them to be "andrewducker.livejournal.com"
3a) If you're already logged in and have given permission to that server to authenticate you to the page you came from then you just bounce back to the "success" page.
3b) If not then you have to log in and then it bounces you back.
4) Success
How would you do this with an email address?
Re: Ask HN: Why not log into web sites via email without any password?
#34Actually, 1Password, a Mac-only app (I think) that I use reminded me of this. For the unaware, the app basically plugs in to your browser and with a "master password" recalls all your logins. I basically go to a webpage, hit the 1p button and I'm golden. If it's the start of a session, I'm asked to enter my master password and that's about it. Obviously the service doesn't have any control of this, and I am reliant o…
The end result is all of your accounts have a different and secure password, whereas you (the end user) only work with the single password.
I've been thinking of giving this a shot but just keep putting it off for various reasons (the long time commitment of resetting all of my passwords to the newer/safer credentials, what if I am on a machine w/o Firefox or the plugin, etc).
Re: Ask HN: Why not log into web sites via email without any password?
#35Earlier quoted context omitted.
The difference between this idea and OpenID is that real people actually know their email address, but not "that thing with all the squigglies in it, you know, the email address for Google". I really, really wish the OpenID standard had used email addresses as the identifier.
The problem is then verifying that that email address _is_ you. With a URL it's trivial. Take mine for instance - andrewducker.livejournal.com 1) Go to that URL. Look for something like this: http://www.livejournal.com/openid/server.bml /> 2) Forward the user there, saying that you're expecting them to be "andrewducker.livejournal.com" 3a) If you're already logged in and have given permission to that server to authen…
My single change to the OpenID spec: perform discovery on a "well known url" on the same domain the email address comes from. After that, its the same as OpenID is now.
Re: Ask HN: Why not log into web sites via email without any password?
#36Re: Ask HN: Why not log into web sites via email without any password?
#37Earlier quoted context omitted.
The problem is then verifying that that email address _is_ you. With a URL it's trivial. Take mine for instance - andrewducker.livejournal.com 1) Go to that URL. Look for something like this: http://www.livejournal.com/openid/server.bml /> 2) Forward the user there, saying that you're expecting them to be "andrewducker.livejournal.com" 3a) If you're already logged in and have given permission to that server to authen…
How would you do this with an email address? My single change to the OpenID spec: perform discovery on a "well known url" on the same domain the email address comes from. After that, its the same as OpenID is now.
Re: Ask HN: Why not log into web sites via email without any password?
#38If the user is logging in with an email account on a domain whose email is handled by an openid provider, it will switch over to logging you in with openid.
Though I'm dubious though about their wording suggestion of "No, help me log in" for the situation where you don't need a password because you can use openid.
A combination of your idea and Google's idea: let users login with only an email address. If the email's domain supports openid, use that, otherwise send an email with a link to log the user in.
Re: Ask HN: Why not log into web sites via email without any password?
#39Earlier quoted context omitted.
The problem is then verifying that that email address _is_ you. With a URL it's trivial. Take mine for instance - andrewducker.livejournal.com 1) Go to that URL. Look for something like this: http://www.livejournal.com/openid/server.bml /> 2) Forward the user there, saying that you're expecting them to be "andrewducker.livejournal.com" 3a) If you're already logged in and have given permission to that server to authen…
How would you do this with an email address? My single change to the OpenID spec: perform discovery on a "well known url" on the same domain the email address comes from. After that, its the same as OpenID is now.
Re: Ask HN: Why not log into web sites via email without any password?
#40I suspect one strong reason against is because it would require you to be near your email client, or to use a webmail service for all online logins. Currently that requirement applies only when you register or forget your password. If your address is a company one, without web access, you won't be able to access any of your online resources. What about the browser automating the procedure to openid?
He's saying the browser would automate the process. Presumably it would speak POP/IMAP and poll your INBOX. Some immediate technical issues here: 1. If you're not using a service with super fast SMTP processing (i.e. Google) your email might not show up immediately. This would delay the login process while you're waiting for the email to arrive. 2. What happens when the email is dropped? (due to some stupid spam IP/D…
I was saying any automation benefit for email would also help openid (for example) because it's already browser-based. If you can automate POP, you can automate openid.