Google Is Finally Making Two-Step Verification Less Annoying (theguardian.com)
Google, which first introduced two-factor authentication about five years ago, is now making it a little easier to utilize this security measure. Instead of users having to manually enter a code that they received in a text message, they will now see a prompt message that only requires them to tap on the phone to approve login requests. The feature will be available on Android as well as iOS soon. The Guardian reports: You do have to turn this service on even if you already use two-step. To turn it on you need to first login to Google and then go to My Account > Sign-in & security > Signing in to Google > 2-step Verification. There you will have options to turn on two-step verification, add Google prompt as an extra form of authentication or replace your existing two-step method. Google isn't the first to use notifications as a method of login verification, both Twitter and Facebook allow users to confirm logins using notifications from their respective smartphone apps. But even they require entering the app, viewing the alert and tapping confirm. Google's one-tap confirm is much faster.
And why on God's green earth would I want to give Google my telephone number?
I like the current setup as it does not require my phone to have a data connection. Not everywhere I have a computer connected to the internet do I have wifi available. The app generating a code seems more flexible in my opinion.
But I don't find SMS two-factor with to be particularly burdensome. It's simple, it works, and it relies only on a de-facto standard method of communication that pretty much everyone already has access to - no vendor lock-in required.
#DeleteChrome
That's not the IT industry, it's the software industry. The IT industry, of course, doesn't allow users to install software willy-nilly, especially if downloaded off the Internet and mindlessly clicking "Yes"/"I Accept" everything.
The point of this form of two-step authentication is that you prove that you have physical possession of the cellphone associated with the account in addition to the password for the account. Having to manually enter a code does not provide any additional security over tapping on the phone - you either have the phone or you don't. So you might as well do it in the most convenient way possible.
LOL, Microsoft has been doing this for a long time already.
So has Duo Security. I wonder what this move by Google will do to their business model.
Does Google allow you to use Google Authenticator?
If you reply, do so only to what I explicitly wrote. If I didn't write it, don't assume or infer it.
It's useless if you don't have a data plan on your phone.
I'm not sure you understand what this does. You might as well say how long do you think it will take for someone to make a fake Gmail app that steals your Google password? Or any other service for that matter? It is a completely orthogonal question to this topic.
Ok, but if they get your phone they can still read the SMS messages so the attack is exactly the same...
Simple: get a new email address only used for "important" logins: emails domain names, everything important to you.
Then stash the login credentials for that one away in a safe or something and hope the provider doesn't delete it because you almost don't use it.
But how else am i going to watch tits.avi.scr.js.jpg.exe.com if I don't click Allow?!
BTW, how many more versions of windows will continue to "hide extensions for known file types"?
If I have been able to see further than others, it is because I bought a pair of binoculars.
This is probably way worse security for the techno-illiterate.
Attacker enters password.
Clueless user gets notification, taps it.
Attacker is let in.
Whereas before it would be:
Attacker enters password.
Clueless user gets a number that they don't know what to do with
Attacker is not let in.
BTW, how many more versions of windows will continue to "hide extensions for known file types"?
I don't expect that to change in any future version of Windows. Here's a link to fix your problem.
http://windows.microsoft.com/en-us/windows/show-hide-file-name-extensions
Ah yes.
That obstacle to logging in, making it impossible to access Google services if you do not carry your phone, lost it, it got stolen, the battery is empty, it crashed, it's out of coverage area.
Not sure how that can be made "less annoying".
Blizzard has similar functionality where the app will look at queued login attempts and ask for approval. Before that, it was IBM's ZTIC which was one of the first 2FA systems which did this.
I wish this were open source, just like TOTP is right now. I use a third party application that allows me to sync my 2FA codes (encrypted, of course) among my devices, including my Linux boxes, and my NAS machines. Having the ability to just tap "approve" for SSH connections would be nice, but it likely would require more moving parts outside my LAN, which could make things less secure.
There are more than just Google's app for authentication. Amazon has similar, and there are a number of third party alternatives, some with dark themes.
I do. I'm nearly 50 years old, have lived in several places, have worked at a number of jobs over the years, had multiple romantic relationships in my life. I've made friends every year, in all of those places, through many diverse ways. Are all of the folks I've friended currently on my short list? No. But that list of a dozen close friends has evolved over time with new ones entering and others dropping off as we move about, go through various stages of life, some have died, etc. But they have my phone number. I have theirs. I may also have their closest friends or family members phone numbers. That adds up to well over a hundred people. And while I'm social I'm nobody compared to some of the butterflies I know. More than two people for every year of life? Those gregarious folks get, and use, that many numbers in a night on the town. No, for most of us non-hermetic folks I'd guess a hundred friends or more is entirely unsurprising.
I don't read ACs: If a post isn't worth so much as a nom de plume to its author then I wont bother either.
If they implement this properly it will be awesome with smartwatches!
My school uses 2FA through a company called Duo and anytime I go to log in to a school website a notification pops up on my Apple Watch and I just need to touch "Approve" and I'm in. No fumbling for my phone or a key-fob... it's instant and convenient... takes all of the pain out of 2FA.
Duo's solution is awesome... even works perfectly with my Apple Watch! When I try to sign on to a website using Duo I get a message on my Watch that allows me to immediately approve the access... without getting out my phone or fumbling for a key-fob.
Can't wait to see this in action in other places! Hopefully Google will add this capability to Authenticator...
While I think this is a good idea... I can kind of understand what he's saying.
Imagine this:
1. Bad guys steal password
2. Bad guys go to gmail.com and enter password
3. Good guy receives notification that approval is needed for a login
4. So used to just clicking Approve for this notification the good guy clicks Approve... and the Bad guys are in.
That scenario couldn't happen with a pin code being sent... because the Bad guys would not receive the pin code and the Good guy wouldn't have anywhere to enter the pin code...
I agree that it's pretty boneheaded... but the point of the parent is that we're all so used to clicking OK/Approve (and we REALLY will be if every website requires this kind of authentication) that many normal people might accidentally click Approve for bad requests...
I have no phone!
Twinstiq, game news
Yes, you can use the FIDO Universal 2nd Factor (U2F) fob.
Change is certain; progress is not obligatory.
Oh, how will you unlock it?
I have a Google account, but I don't have gmail.
If my e-mail is somehow compromised regardless, I could unplug the server?
Change is certain; progress is not obligatory.
You have to unlock the phone first...
Change is certain; progress is not obligatory.
BTW, how many more versions of windows will continue to "hide extensions for known file types"?
Before you complain about this ask yourself:
1) Did people know what a filetype was?
2) Did the rate of success for these attacks change dramatically as a result?
The most common infection vector for these types of files do NOT go through windows explorer. They are downloads complete with box asking if you want to open the file, or email attachments which show the file name in full. People were fooled before, people will continue to be fooled, and hiding or showing the file extension in an operating system doesn't change this one bit.
I've been doing this for months. I'm sure the service has been available for much longer.
You don't when using Duo at least...
But without google.
Something like an android app and some web service coupled with a pam module. The login prompt then displays a number, the app displays the number as well and i can accept the login from the app with a single tap. Fallback to normal google authenticator.
Another alternative is to use TOTP (Time-derived One-time password):
an ever changing code that is based on a hash, computed out of the current time (hence the ever changing) and a shared secret that only you and google know.
Only someone possessing the shared secret can compute the correct code for that time.
The secret itself is never sent on the wire, only the current-time code derived of the secret is.
You can find apps running on tons of other hardware if you don't own an Android nor an iPhone (or simply don't want to give that phone number to google).
You could even built your own, using an Arduino, an LCD display and some mean to get accurate(-ish enough*) time (e.g.: GPS chip or a DCF77 receiver if you're in Europe, or a RDS FM radio receiver, or extract it from TV broadcast, etc.)
TOTP is supported as a two-factor standard at lots of other companies (Facebook has it as a possibility, nearly every bitcoin-related website I've seen has it, Microsoft too, etc.)
(*) - a new code gets generated every 30 seconds, and some server-side implementation also compare against the past couple of code.
So your clock doesn't necessarily need to be that much precise.
You could get the time from your wrist watch if you don't have any time source.
Or you could run the TOTP *on* the wrist watch if yours happen to be programmable (e.g.: Pebble)
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]