3 ms·
I happen to love Google's two-factor authentication, and, every so often, I go through and just revoke all of the "application specific passwords", just to clea
by ghshephard 15y ago
I happen to love Google's two-factor authentication, and, every so often, I go through and just revoke all of the "application specific passwords", just to clean things up, and then recreate the five or six that I actually use.
It feels great to know that I've got a single console that informs me what applications and machines can access my gmail - and I don't have to worry about an old laptop out there somewhere with the password cached.
And - what does the author propose as an alternative if not application specific passwords? How else do I let my iPhone's iMap client read Gmail?
The only feature that I'd like more, would be the ability to limit the cookie to something less than 30 days. I'm pretty used to typing in my OTP at work multiple times a day to login to various systems, so having google request me authorizing my system at the beginning of day/week would be fine.
Other than that - I think Google sets the bar in terms of web application security.
- pavel_lishin 15y ago> what does the author propose as an alternative if not application specific passwords? How about limiting each password to a single use? I generate a password so I can check my e-mail with my iPhone - and after that, the password should become unusable. (In fact, bonus points if I receive an alert that someone has tried to use that password.)
- FaceKicker 15y agoThat wouldn't work unless the iPhone only has to log in one time, or if you want to have to generate an application-specific password every time you want to check your email.
- pavel_lishin 15y agoI honestly have no idea how it works. I thought that the Mail app would login once, and store some sort of 30-day auth token.
- Mavrik 15y agoEr, no. IMAP requires you to send password (encrypted or no) every time you connect.
- mike-cardwell 15y agoFYI, you can authenticate against both Googles IMAP and SMTP submission services using OAUTH. * CAPABILITY IMAP4rev1 UNSELECT IDLE NAMESPACE QUOTA ID XLIST CHILDREN X-GM-EXT-1 XYZZY SASL-IR AUTH=XOAUTH 250-AUTH LOGIN PLAIN XOAUTH
- ConstantineXVI 15y agoThe client has to support it though; can't think of a mail client I've used with oAuth support.
- mike-cardwell 15y agoOAuth was added so apps could be built which are able to access other peoples gmail accounts, but without sharing credentials. I believe there are web apps which utilise this OAuth capability, but I haven't come across any desktop apps which use it. My point still stands though, which is that you can use IMAP without passwords.
- watty 15y agoThey should be "application specific", maybe even with options to choose which parts of Google Services it can access. I don't want my Digsby generated password to be able to access my email via IMAP. It's unlikely to be leaked in plain-text but it's silly to call it application specific.
- tlrobinson 15y ago> what does the author propose as an alternative if not application specific passwords? Actually restrict the "application specific passwords" to one application. The definition of "one application" could simple like the protocol (IMAP, CalDAV, Chrome sync, etc), or complex like an application-specific "signature" that changes between implementations/versions, or restricted to an IP address, etc.