Slashdot Mirror


Less Than 1 in 10 Gmail Users Enable Two-Factor Authentication (theregister.co.uk)

It has been nearly seven years since Google introduced two-factor authentication for Gmail accounts, but virtually no one is using it. From a report: In a presentation at Usenix's Enigma 2018 security conference in California, Google software engineer Grzegorz Milka this week revealed that, right now, less than 10 per cent of active Google accounts use two-step authentication to lock down their services. He also said only about 12 per cent of Americans have a password manager to protect their accounts, according to a 2016 Pew study.

254 comments

  1. Yes! by Anonymous Coward · · Score: 0

    I may not be part of the 1%, but I'm part of the 10%.

    1. Re:Yes! by dgatwood · · Score: 1

      Those numbers are completely absurd. Chrome + Safari alone is 70% of the browser market, and those both have built-in password managers.

      So 58% of computer users don't know that they're already using a password manager.

      Really?

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    2. Re:Yes! by DickBreath · · Score: 4, Funny

      I'm not going to use 2 factor because I don't want Google to know my gmail address.

      --

      I'll see your senator, and I'll raise you two judges.
    3. Re:Yes! by pjt33 · · Score: 1

      Just because my browser has a built-in password manager, doesn't mean I use it. I use Keepass instead, and I have no idea how Google would know that, so I wonder what the basis for their statistic is.

    4. Re:Yes! by ShanghaiBill · · Score: 2

      Just because my browser has a built-in password manager, doesn't mean I use it. I use Keepass instead

      You aren't using it because you are already using something else. But for 90% of the public, if a popup asks "Do you want Chrome to remember this password?", they are going to think "Sure, why not?". But if someone later asks them "Are you using a password manager?", they will say "No", because they don't even know what that is.

    5. Re:Yes! by Anonymous Coward · · Score: 0

      Anyone clicking "Yes" on a "Remember the password for this Site?" prompt in Chrome, Firefox or Safari is a complete moron. Why would anyone trust Apple, Google or Mozilla with the Keys To Their Kingdom? I might have trusted Mozilla with them a decade ago, but not any more.

    6. Re:Yes! by Anonymous Coward · · Score: 0

      I'm using 1password, but Google probably thinks I'm using their shit.

    7. Re:Yes! by TemporalBeing · · Score: 1

      Just because my browser has a built-in password manager, doesn't mean I use it. I use Keepass instead, and I have no idea how Google would know that, so I wonder what the basis for their statistic is.

      So Chrome doesn't necessarily use it's *built-in* password manager either. If the system provides one (e.g GNOME, KDE) then it will automatically use that; you can also configure it to use another one. I believe there are LastPass and KeePass extensions for Chrome to use them instead of the built-in supported ones too.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    8. Re:Yes! by swillden · · Score: 2

      Anyone clicking "Yes" on a "Remember the password for this Site?" prompt in Chrome, Firefox or Safari is a complete moron. Why would anyone trust Apple, Google or Mozilla with the Keys To Their Kingdom? I might have trusted Mozilla with them a decade ago, but not any more.

      If you use your gmail account as the primary account on all of your other sites, you are trusting Google with the Keys to Your Kingdom. Substitute whatever email service provider you use, because anyone who controls your email can almost certainly reset the password on any other account you have, unless that other account has some 2FA of its own. Security questions are weak in general, but even weaker against someone who has all your email and can mine it for answers.

      Also... you're apparently saying that you trust Google, Mozilla or Apple enough to type your passwords into their browsers but not enough to use their password storage solutions. Does that make any sense at all? The only way it makes sense is if you assume that they're not competent to properly secure the password database (which is fairly easy), but are competent enough to get the rest of the security right (which is very hard). It clearly makes no sense if you assume they might be maliciously interested in stealing your passwords, because you're typing your passwords into their browser.

      And, FWIW, if you set a sufficiently-long sync password on Chrome, Google has no access to the passwords that Chrome stores for you. Yes, they all get uploaded to Google, so they can be synced between Chrome instances on different machines, but they're all encrypted with your sync password.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:Yes! by TemporalBeing · · Score: 1

      Those numbers are completely absurd. Chrome + Safari alone is 70% of the browser market, and those both have built-in password managers.

      So 58% of computer users don't know that they're already using a password manager.

      Really?

      TFA isn't talking about Password Managers but about 2-Factor Auth which is entirely different from using a Password Manager. A Password Manager is only good for storing one of the two factors; the second factor is dynamic and comes via YubiKey, soft-key (GAuthenticator), SMS/TXT, etc.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    10. Re:Yes! by taustin · · Score: 1

      My /. password hardly constitutes a kingdom. Honestly, I don't give a crap if Google has it. And neither does Google.

    11. Re:Yes! by sexconker · · Score: 1

      100% correct. Handing passwords over to a third party like that is retarded. KeePass is the correct solution.

    12. Re:Yes! by sexconker · · Score: 2

      The "second factor" in most cases can absolutely be put into something like KeePass if you have the plugins to work with it. It's just a seed you jam into a hashing algorithm along with the current time.

      The only ones you need a third party for are those which are unknown to you (an awful idea). For example, a site sending you a one-time code (randomly generated, hopefully) via text or email. That's not 2 factor, that's 2 channel. (And SMS is a joke in terms of security, and email just verifies the person logging in has access to that email, there's not actual check that they are the person they claim to be.)

      Multi-factor authentication traditionally relies on 3 things. Something you are (a fat, ugly slob), something you have (the worst BO of all time) and something you know (a password). In the real world this works just fine. The guard at your workplace knows you, asks to see your badge, and you put in you password into whatever terminal. There is active verification of these 3 different types of criteria. On the internet, they try to ape that security but in the end it's all "something you know". Whether that's the password, the seed for somsone's password-generating clock, their phone number to pull the SMS down, a hash of their retina/fingerprint/anus/etc. it doesn't matter.

    13. Re:Yes! by Darinbob · · Score: 1

      If my bank asked me to use two factor authentication, I would consider it, as my bank account needs to be secure. But for google, why? It's fluff, I could lose the account tomorrow and not much would happen. I don't have it linked to any credit card numbers, identification numbers, etc.

      So why are fluffy social media sites and games encouraging this, but important stuff that need security is not?

      Anyway, two factor means I have to have my phone all the time, and if I lose or sell it I am going to have a major hassle trying to get back into my account. I don't want Google of all people to have this information sort of information.

    14. Re:Yes! by Darinbob · · Score: 1

      I had to train my mom not to do this. She lost her Firefox profile e and could not remember any of her passwords, and important the profile from an old computer wasn't working. She wrote them down in a file but in a really jumbled up manner that I couldn't make sense of. I eventually figured out how to decode the profile that had the passwords. But until then we had no access to the ISP and I was ready to go and beg with them over the phone or in person to reset the password.

    15. Re:Yes! by bingoUV · · Score: 1

      competent to properly secure the password database (which is fairly easy),

      If they are competent, then they must be unwilling to secure it. In 2018, this worked for my experimental chrome browser , latest from Google at the time :
      https://it.slashdot.org/story/...

      Creative uses of Spectre (and Meltdown or something like it as an additional help) can make it even more "fairly easy" to steal the passwords.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    16. Re:Yes! by MoarSauce123 · · Score: 1

      The passwords are kept in local encrypted storage...at least that is what the password manager is supposed to do. Not sure how the Google account syncing goes. Remembering passwords is fine, autofilling in passwords is a major security issue and this is why reputable browsers turned that off. There is some inconvenience, but looking up the password in the password manager is not that difficult.

    17. Re:Yes! by swillden · · Score: 1

      competent to properly secure the password database (which is fairly easy),

      If they are competent, then they must be unwilling to secure it. In 2018, this worked for my experimental chrome browser , latest from Google at the time : https://it.slashdot.org/story/...

      Meh. It's no surprise that browsers don't yet mitigate a barely-published attack, particularly since it's arguably not an attack at all. The browser is doing the right thing and filling username and password fields for the site that it's supposed to. The site developer is the one including hidden forms that send that data to the wrong place. Bad/buggy web sites can do all kinds of nasty things with/to the data you give to those sites. The only difference here is that the site developer doesn't realize he's added this particular nastiness, but he did make the decision to use a shady tracking service.

      Creative uses of Spectre (and Meltdown or something like it as an additional help) can make it even more "fairly easy" to steal the passwords.

      Again, not an issue with having a password database in your browser. An issue with entering passwords in your browser at all, of course (or potentially in any program on your computer), but not a reason to prefer typing passwords over using the browser's password keeper.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    18. Re:Yes! by bingoUV · · Score: 1

      Yup. Blaming the attacker completely absolves the maker of vulnerable software. What else can I expect from Google employees?

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    19. Re:Yes! by swillden · · Score: 1

      Yup. Blaming the attacker completely absolves the maker of vulnerable software. What else can I expect from Google employees?

      Umm, you need to re-read the post you're replying to. Nowhere did I blame the attacker.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    20. Re:Yes! by bingoUV · · Score: 1

      Site developer

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    21. Re:Yes! by swillden · · Score: 1

      Site developer

      Yes. Not the attacker, the site developer who chose give your password to his site to an tracking company. He could have chosen to do it directly, instead he just included their content and scripts on his site, from his domain, essentially enabling them to do an XSS attack on his site without needing the "XS" part.

      In general, there's very little browsers can do to prevent XSS if site developers don't build their sites correctly. What we have here is a case where site developers may have done a decent job of preventing general XSS attacks, then gave a specific attacker special privileges. In this particular case, there may be some things that browsers can do about it, now that researchers have pointed out the issue. However, that won't actually fix the general case, because sites allow these tracking networks to inject Javascript as well. If the tracking companies wanted to, they could inject Javascript that collects your username and password from the visible fields, when you type them.

      The only real solution is for site developers to be careful about whose content/code they inject in their sites. When they contract with an analytics company, they should ensure that the contract contains a commitment not to snarf extra data.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    22. Re:Yes! by bingoUV · · Score: 1

      The
        site developer "chose give your password to his site to an tracking
      company" , which was given to the site developer by the browser. The
      user did not give the password to the site developer via the browser.
      User gave the password to another site developer, but also made the
      mistake of storing it in the browser. So the browser went ahead and gave
        the password to this "malicious" site developer.

      It is extremely dishonest of you to mention " tracking company ". Any
      use can be made of the " stolen " password, not just tracking.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    23. Re:Yes! by swillden · · Score: 1

      The site developer "chose give your password to his site to an tracking company" , which was given to the site developer by the browser. The user did not give the password to the site developer via the browser.

      By "site developer" I mean the author of the site the user visited. So, yes, the user did give the password to the site developer; the user has to do that to log in.

      It is extremely dishonest of you to mention " tracking company ".

      Huh? I'm beginning to think you don't understand the issue that you cited.

      Let me be very clear, with an example. Let's use slashdot. Suppose that slashdot made an agreement with one of the tracking services, say AdThink, that has been found to be exploiting this "vulnerability". AdThink gives some value to slashdot, and slashdot includes AdThink's content and supporting JavaScript in the content delivered on the slashdot home page.

      Now, you, the user, have your browser remember your slashdot login. The browser watches for username/password forms from the slashdot.org domain, and when it sees some, it fills them in with your values. It does not click "Submit" for you, you have to do that yourself. AdThink wants your slashdot login information, so in the content that it gives to the slashdot devs to inject in to the home page, it includes a hidden form which has a username and password field. Note that developers who build the slashdot site not only allowed this, they actively worked to serve up AdThink's malicious code. AdThink also includes a bit of Javascript that detects when data is entered on the hidden form and submits it. Because all of the Javascript and hidden content was served from slashdot.org, the same-domain policy doesn't prevent any of this, even though the target of the form is an AdThink server, not a slashdot.org server.

      The key point here is that it's slashdot who provided all of the malicious HTML and JS to your browser. Your browser has no reason to distrust this content any more than the password entry form that you type stuff into yourself.

      Make sense?

      With that understanding, it should also be clear that AdThink doesn't even need password auto-filling to do this. They could also inject some Javascript that hooks in the the events that are generated when you manually type in your username and password, and it could generate a call back to the AdThink server providing your data then, too.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    24. Re:Yes! by bingoUV · · Score: 1

      You have no clue about the issue I cited.

      Slashdot is the original site to which the user supplied the password. And the user made the mistake of saving it in the browser. No decision on the part of Slashdot is now required. The user, independently of Slashdot , 2 days later, now goes to a COMPLETELY different site. Read :

      To start, we'll need you to save some test credentials using the form below. On a later page, we'll demonstrate how a third-party script can retrieve these saved credentials. Note that the third party does not need to be present when the credenitals are saved, and that none are present on this page.

      The new , third party, site is a malicious site. The developer of which is an attacker. Whom you are blaming in trying to unsuccessfully defend the vulnerable software. Which is the browser. Specifically the password manager part of the browser.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    25. Re:Yes! by bingoUV · · Score: 1

      So?
        How much does Google pay for your soul ?

      If Google is sending the likes of you to defend the password managers of
        all browsers, some not even developed by Google, I suspect Google is exploiting this vulnerability.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    26. Re:Yes! by swillden · · Score: 1

      I could dig in and explain in more detail why you're wrong, but I'm not interested in educating assholes. I ignored your first few jibes, but I'm done now. You can feel free to think what you like about me -- you will anyway. And Google has nothing to do with my posts on /., except to officially discourage me from making them (but not enough to actually tell me that I must stop).

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    27. Re:Yes! by bingoUV · · Score: 1

      Yes, you have completely misunderstood the vulnerability, and looked like a complete idiot so far to spare my feelings.

      BTW I interact with the likes of you only because the world is a better place with someone taking on your lies.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
  2. That's a lot! by Anonymous Coward · · Score: 1

    That's a lot considering how many email boxes they have.

    1. Re:That's a lot! by Oswald+McWeany · · Score: 1

      That's a lot considering how many email boxes they have.

      Yeah... I have about a dozen gmail accounts. They all forward to one of my two master-gmail accounts. THOSE are locked down with 2-factor authentication. The others are just junk e-mail accounts that I don't care if they get hacked. I don't bother with those. I don't know how many people are like me and have multiple dummy e-mail accounts per real account, but I suspect it's a lot. I also suspect people care a lot less about the security on their dummy e-mail accounts.

      Most e-mail accounts are probably dummy accounts. Especially on a free service like gmail.

      --
      "That's the way to do it" - Punch
    2. Re:That's a lot! by Jane+Q.+Public · · Score: 1

      I only use gmail for junk mail.

      Why bother to "secure" an email account when Google is going to read all the mail and sell your information anyway?

      Seems kind of pointless.

  3. does it get all up in your face by Anonymous Coward · · Score: 0

    and say your sextual emails will be stolen
    that your bank will be hacked
    that you will send virusii to your coworkers

    if the answer is no johnny gmail user aint turning it on

  4. Dont trust by Anonymous Coward · · Score: 0

    So far I don't trust any of the password managers available for mobile. Better to keep it all in my head.

    1. Re:Dont trust by DontBeAMoran · · Score: 0

      What if you lose your head someday? How will you get your passwords back?

      --
      #DeleteFacebook
    2. Re: Dont trust by Anonymous Coward · · Score: 0

      I'll give him head. I'll give him LOTS of head!

    3. Re:Dont trust by Oswald+McWeany · · Score: 1

      So far I don't trust any of the password managers available for mobile. Better to keep it all in my head.

      Exactly my thinking. With a password manager they only need to get past one password to know everything. Not just what all your passwords are, but all the websites you have passwords for.

      --
      "That's the way to do it" - Punch
    4. Re:Dont trust by gnick · · Score: 1

      With a password manager they only need to get past one password to know everything.

      If you decide to put all your eggs in one basket, WATCH THAT BASKET!

      --
      He's getting rather old, but he's a good mouse.
    5. Re:Dont trust by Anonymous Coward · · Score: 0

      If on Android and using a firewall, there are password managers which require zero network permissions.

      It depends on your level of convenience versus security:

      Most secure is the above.
      Next comes apps like enPass, Codebook, SafeInCloud which can store locally, but store data on one of your existing cloud providers.
      Then comes apps like LastPass and Dashlane which have known good security, resisted attempts, and have some solid assurance of secure storage.
      Then come apps like 1Password, mSecure, and others which require you to use their cloud provider, or require you to have an account with them before you can sync with other places. Both 1Password and mSecure have previous versions that don't require this, but other PW managers may.

      With apps that require to use their cloud like mSecure, and have zero mention of compliance, don't use them. I like using DashLane or LastPass for common stuff, but personal stuff that needs secure like 2FA codes which I want to export to a text file for safekeeping, EnPass and Codebook are excellent. SafeInCloud is also great, but it comes from Moscow, so even though it likely is trustworthy, the origin is worth mentioning.

    6. Re:Dont trust by gbjbaanb · · Score: 1

      Not so, they need to get past a password *and a key file*. Keepass stores it all locally, and (optionally) requires a file to decrypt as well as password.

      Can be awkward putting your keyfile somewhere secure and fetching it on mobile (unlike a PC where you can keep it on a USB drive that you remove when not using it) but it can be done if you're paranoid by storing it on the cloud or remote location, or even just obfuscating it by using an ordinary file such as a picture or music mp3 as the keyfile.

      If everytime you open your DB you have to select the file (and set it to not remember the history, obviously) then you're as secure as anything, particularly if you use 1 picture out of a folder full of a thousand.

    7. Re: Dont trust by DickBreath · · Score: 1

      What if he has only one head to give?

      You can only behead them once. if that is what is mint by losing your head.

      --

      I'll see your senator, and I'll raise you two judges.
    8. Re:Dont trust by Anonymous Coward · · Score: 0

      So far I don't trust any of the password managers available for mobile. Better to keep it all in my head.

      Exactly my thinking. With a password manager they only need to get past one password to know everything. Not just what all your passwords are, but all the websites you have passwords for.

      You're screwed either way. Is it to have a password manager generate and remember all of your passwords, but protected with the strongest password you can remember or is it better to keep dozens, potentially hundreds (or more) username/email combinations in your head where you will have to: reuse passwords or use variations on your 'standard password' or remember whatever method you use to generate passwords *and* never conflate the username/password pairs *and* hope that you remember the account credentials for that one account that you logged into two years ago, but you really need back into it now because of (insert reason here).

      Part of this, of course, is that just about every site on Earth now wants you to create an account just to use the service, or even to see anything beyond the landing page, which, of course, is a rant for another time.

    9. Re:Dont trust by Cajun+Hell · · Score: 1

      The head manager handles that.

      --
      "Believe me!" -- Donald Trump
    10. Re:Dont trust by graymatter1945 · · Score: 1

      With 1Password you don't have to use their cloud. You can still buy the non-subscription versions and use Dropbox. mSecure 5.5 allows wifi or cloud sync without using their cloud.

    11. Re:Dont trust by WinstonWolfIT · · Score: 1

      Pro tip: 2fa on the password manager.

    12. Re:Dont trust by ctilsie242 · · Score: 1

      It is about shifting security risks around. Using the same (or a similar) password on multiple sites versus a PW manager allowing for more secure entries per site.

      In the past, I just did a MD5 of my master password and the site name and used that, but with the varying length, character, and other requirements sites have, that isn't as feasible as it used to be.

      The question is... is the risk of the master password being lost greater than someone figuring out that you use a similar PW on a bunch of sites to get in? I prefer to use solid passwords with every site, so I take the PW manager risk. If someone is keylogging my machine, I'm hosed anyway, and that is what 2FA is for.

    13. Re:Dont trust by Dragonslicer · · Score: 1

      With a password manager they only need to get past one password to know everything. Not just what all your passwords are, but all the websites you have passwords for.

      But they would also need access to the password store file, which should only be on your computer. The main advantage of a password manager is that you can have different, complex passwords for each site, so that if one of those sites has a data breach (which you'd be assuming is more likely than having your personal computer compromised), the attackers don't get your password to a bunch of other sites.

    14. Re:Dont trust by Shikaku · · Score: 2

      My keyfile is the a specific string of text (with no returns to avoid the /n/r and /n text file differences between Windows and *nix). That way I can't lose it unless I forget that string of text, and I can easily remake it if need be from any text editor.

  5. No thanks. by b0s0z0ku · · Score: 4, Insightful

    Not everyone wants to give Google more personal info -- working phone #, alternate email, etc and so forth.

    Also, this doesn't work well with standards-compatible email clients like Thunderbird or K-9.

    1. Re:No thanks. by Anonymous Coward · · Score: 1

      You can generate non-recoverable application-specific passwords through account settings to bypass 2FA requirements for clients where it doesn't play nicely. Arguably that could defeat the purpose, except if someone manages to actually get that password, you're already thoroughly owned and it's a moot point.

    2. Re:No thanks. by Anonymous Coward · · Score: 1

      Actually, that's not a problem anymore, but google has failed to make users aware of this. I myself wasn't using 2FA until about a month ago, not because I didn't want to give google the info (they already had it) but simply because it wasn't convenient. Most of the time I'd need to authenticate with it, I'm in an area with no cell signal, thus cannot receive a text. Other options were a PITA. But recently I realized there are now better options for using 2FA

      With Android, google makes authentication very easy with the Google Authenticator app (and I assume there is something similar for iOS). You just confirm the login on your cell phone and it lets you in. It also supports one of those virtual tokens with the changing 6 digit number (which I assume would allow you to login by getting the number off your phone even if you don't have internet access on it). With this, 2FA is not really inconvenient for me anymore.

    3. Re:No thanks. by forgottenusername · · Score: 1

      So getting all your email isn't a concern but getting a few minor additional bits of information is? Anyway you can just use their authenticator and print off emergency-use codes, no need to give them additional info.

      Run your own mail server if you're that concerned, it's not very difficult. You could even do it in aws quite cheaply; they will setup reverse DNS for a static (elastic) IP if you fill out a form.

      If that is too insecure, I suggest writing encrypted letters to folks and making sure they have a decryption pad. One time use, of course.

    4. Re:No thanks. by Anonymous Coward · · Score: 0

      Why not cut head off? I already have a wound.

      God damn, millennials are stupid. God help us.

    5. Re: No thanks. by Anonymous Coward · · Score: 0

      Hogwash on both counts. The Google authenticator generates codes which change continuously. You just need to install an app, which requires no login and does not have to be the one provided by Google. As for alternative clients, you can generate "app passwords", which are just passwords that can be revoked. With all that said, being worried about your privacy while using Gmail is a bit like being worried about the honesty of new hires and then hiring exclusively from the local jail.

    6. Re:No thanks. by chispito · · Score: 2

      Not everyone wants to give Google more personal info

      How is giving Google your phone number more worrisome than giving Google all of your correspondence?

      --
      The Daddy casts sleep on the Baby. The Baby resists!
    7. Re:No thanks. by Fuzi719 · · Score: 1

      Every time I've tried to use the Google Authenticator app, the codes it gives aren't accepted. I get an error that it is an expired code, even when I refresh the app over and over. I've had to use two of my six emergency codes already because the Authenticator app just doesn't work. And yes, I've done the "sync time" many times, it doesn't do anything, says it is already sync'ed.

    8. Re:No thanks. by gbjbaanb · · Score: 1

      One thing to be very aware of with Google Authenticator is that if you move phone, you have to be very careful or all your auth will remain tied to the old phone. People have complained about this and it can be a very serious problem for you.

      Other apps allow you to migrate your registered auth to new devices. Authy is much better, and provides you with a sync option.

    9. Re:No thanks. by DickBreath · · Score: 1

      Yeah. Only one factor. Not two factor.

      If there is only one factor then prime factorization won't work because the single factor is prime.

      --

      I'll see your senator, and I'll raise you two judges.
    10. Re:No thanks. by Anubis+IV · · Score: 1

      Not everyone wants to give Google more personal info -- working phone #, alternate email, etc and so forth.

      I certainly understand (and share) this concern, but that's a problem with having a Google account at all, rather than a problem with enabling 2FA on an existing account, since they don't require any of those details when setting up 2FA. With my current Google account, I gave them the bare minimum during account creation. They don't have any of my phone numbers, they don't have my real name, and the only reason they have an alternate e-mail address for me is because I registered my account using that address so as to avoid tying my Google account to a Gmail address. And even that e-mail address is useless to them, since it was a one-off I set up in Fastmail that's unique to Google (e.g. google@spam.example.com).

      In terms of setting up 2FA, I simply enabled it on my account, used my iPhone's camera to scan a QR code into my third-party password manager, and I was done. No need for divulging personal info. My password manager simply parsed the standards-based shared key from the QR code and is now able to generate and auto-fill the necessary OTPs on an as-needed basis whenever I'm logging in via the web on any of my devices.

      Also, this doesn't work well with standards-compatible email clients like Thunderbird or K-9.

      Yes, it does. For apps that support standards-compatible OTP entry, you'd simply enter the OTP when prompted, same as you would on the web or anywhere else that supports these standards. For apps that don't support these standards, you'd instead go to your Google settings and generate a unique, revokable "app password" for each app that you want to grant access, same as with every other decent 2FA solution I'm aware of.

      Look, I like bashing Google as much as the next guy (check my extensive comment history if you don't believe me), but pretty much all of what you've said is baseless when it comes to Google's implementation of 2FA.

    11. Re:No thanks. by TheReaperD · · Score: 2

      More to the point, Google already knows your real name, address, phone numbers, sexual preferences (even ones you've never told anybody), shopping habits, travel behaviors and more than I can imagine. So, what difference does it make? Either don't use their service because you don't like the company's behavior (not going to change what they know about you, in this case), or use it to it's fullest potential and get over yourself.

      --
      "Be particularly skeptical when presented with evidence confirming what you already believe." -
    12. Re:No thanks. by chronoglass · · Score: 1

      not entirely true, you can just go to the 2fa web site and login without needing 2fa and turn it off, then back on. it will require a reenroll.. but hey, at least there is a security flaw to exploit when yer hosed, and only when yer.. wait...

    13. Re:No thanks. by Actually,+I+do+RTFA · · Score: 1

      Nor do I want to be coerced into carrying a cell phone everywhere to access email; a service I should be able to use from a random terminal.

      --
      Your ad here. Ask me how!
    14. Re:No thanks. by Anonymous Coward · · Score: 0

      Sure it does.

      1. use the only real and good 2FA. either TOTP phone app like google auth, or hardware based U2F. Don't trust google auth for a google acount? There is redhat developed FreeOTP in f-droid and play store which is %100 compatible, and FOSS. There is also support for U2F, which is a standard for interchangeable hardware tokens. very easy to sync them to an account, and just press button to log in. yubikey makes a very secure key that anyone shy of a nation state actor, and even then won't be able to break.

      2. in addition to 2FA, set and app password. App passwords are randomly generated per device password. they cannot be retrieved once set, but can be canceled at any time. Especially for a phone, use an app password for all third party clients to severally limit damage in case of compromosie. I.e. can be revoked without changing main password, and will not give hints about your password you likely reuse. That password only works with 2FA anyhow.

    15. Re:No thanks. by Anonymous Coward · · Score: 0

      Very much so. Also here's something I don't like: if I have 2FA enabled, and my phone is stolen, how do I now access my email? Without 2FA I just do what I always do: goto the webpage, login, possibly change password if I'm worried I left my phone logged in (unlikely) or let it record my password (not gonna happen), read email, logout. With 2FA I can't read the authentication txt so I'm stuck.

    16. Re:No thanks. by Anonymous Coward · · Score: 1

      More to the point, no they don't because I'm not a feckless millennial. God damn I hate millennials, especially western ones. They deserve 110% of the screwing they get from corporations.

    17. Re:No thanks. by Anonymous Coward · · Score: 0

      They don't get 'all my email', just the ones from people who I happen to have given that address to. Unlike a phone number, an email address is free and disposable and is therefore less likely to be associated with everything a privacy-aware individual does.

    18. Re:No thanks. by TheReaperD · · Score: 1

      I'm not a millennial; not even close. If you think Google doesn't have this data on you, you're both naive and delusional.

      --
      "Be particularly skeptical when presented with evidence confirming what you already believe." -
    19. Re:No thanks. by AaronW · · Score: 1

      I just had to do a factory reset of my phone, which removed the authentication support using my phone. I just went to Google and used the change phone option and scanned the QR codes to re-add it to my phone.

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    20. Re:No thanks. by Anonymous Coward · · Score: 0

      Not everyone wants to give Google more personal info -- working phone #, alternate email, etc and so forth.

      Also, this doesn't work well with standards-compatible email clients like Thunderbird or K-9.

      That too, all this two-factor stuff being forced on us breaks all those convenient time-saving aggregators I like to use.

    21. Re:No thanks. by thegarbz · · Score: 1

      Not everyone wants to give Google more personal info -- working phone #, alternate email, etc and so forth.

      It's cute that you don't think Google knows this already.

    22. Re:No thanks. by Anonymous Coward · · Score: 0

      Its a dependency issue. I do not want to rely on Google anymore.

    23. Re:No thanks. by Spamalope · · Score: 1

      I prefer to give them less real info, and make sure to salt everything they get with fictitious info to poison their well. Hiding info from the stalker vaccum cleaner is tough, but getting it to take more info is easy.

    24. Re:No thanks. by Riceballsan · · Score: 1

      While I agree some security conscious people do in fact feel that way, I'd still say that is far more likely nowhere near a significant percentage. I'd be willing to bet that in percentages of reasons. 10% use 2f 85% either are unaware, consider it too much trouble, got annoyed with it taking more than 15 seconds to log in at their school/work etc... and turned it off etc... They probably still already gave google all that information as password reset options. 5% worry about giving google more information, or have actual programs that are incompatible.

    25. Re:No thanks. by Anonymous Coward · · Score: 0

      I am running into a lot of sites now that are enabling 2FA by default. This is absolutely worthless when they want to use a text message for it as I have NO CELL coverage at home. I'm not going to drive to town to check my email.

      LOL @Captcha: alphabet

    26. Re:No thanks. by apoc.famine · · Score: 1

      Which quite likely contains your phone number, along with a easily parsed string of text like, "and you can reach me at nnn-nnn-nnnn."

      --
      Velociraptor = Distiraptor / Timeraptor
  6. Sure... by Anonymous Coward · · Score: 1

    It's a fucking pain in the ass to use, and if you're into security, you're not using gmail...

    1. Re:Sure... by arth1 · · Score: 1

      It's a fucking pain in the ass to use, and if you're into security, you're not using gmail...

      A problem is that software providers have taught users that authentication and authorization is the same thing, when they're not.
      Users expect a single operation.

      This is unlike real life, where people seem to have less problems distinguishing the two. If you go to the bank and fill out a withdrawal slip, you authorize it with your signature, but need to show an ID to authenticate yourself. The two tasks aren't combined.

      Biometrics and RSA key generators = authentication
      Passwords = authorization

      Programs including GMail should separate the two, and ask for what they they need when they need it, so it makes sense to the customer.

    2. Re:Sure... by mencik · · Score: 1

      Passwords, Biometrics, and RSA key generators are all authentication. None of them are authorization. The distinction is "what you know" vs. "what you are" vs. "what you have". Using more than one of those methods is simply "multi-factor authentication". Authorization is a whole other ballgame.

    3. Re:Sure... by arth1 · · Score: 1

      No, passwords are authorization. It's something you know, and which can only be given with your approval.
      Biometrics and RSA keys are something you are or have, and thus authentication. It's something that can be given without your approval.

      Clicking "OK" when authenticated does not imply authorization, although that's how most systems are designed. It's wrong, wrong, wrong.

      The problem is that we are too lazy to give authorization, and bind the two together as if they were the same thing. They aren't, and "two-factor" is not the solution, it's propagating the problem of not keeping the two separate. Making authentication more safe does nothing for the problem of authorization, and vice versa.

    4. Re:Sure... by mencik · · Score: 1

      Sorry, but you are wrong. "something you know, something you are, and something you have are all ways to authenticate. Authorization is deciding what you are allowed to see after you have authenticated that the identity you claimed is correct. In this case, gmail assumes you are authorized for all aspects of your account once you have authenticated, but whatever means you use. I invite you to read this discussion on authentication vs. authorization to learn the difference. https://stackoverflow.com/ques... There are plenty of other articles to read to learn the difference. But, no matter how you slice it, passwords are just another way to authenticate your claimed identity.

    5. Re:Sure... by arth1 · · Score: 1

      No, something you know does not authenticate you. This is the entire problem with the standard approach to authentication. Too many people think this is the case, but like so many things that everybody knows, it's just plain wrong.

      The standard username/password query is:
      Username: yadda
      Password: foobarbaz

      Ok, you have now told that you know the foobarbaz passphrase, but who are you?. It's authorization, because it can be shared. I can authorize someone to act on my behalf. But they don't become me.

      Biometrics is like the username. It only tells who you are.
      A two factor authentication is just that - authentication, helping verify who you are. not what you allow.
      A password is something you know, and authorizes the action, whether it is you or someone else.

      The common approach of bundling the two together is what causes all these problems. It's convenience, pure and simple. But not secure.

    6. Re:Sure... by sexconker · · Score: 1

      Passwords are not authorization.
      Authorization is handled entirely by the service.

      Authentication:
      User: Hello, I am Bob.
      System: Hello, Bob. Please prove you are Bob.
      User: Here is the password for Bob.
      System: Please provide additional information.
      User: Here is a hash of a scan of my anus.
      System: Welcome, Bob.

      Authorization:
      User: I would like to look at Bob's order history.
      System: Here you go.
      User: I would like to look at Joe's order history.
      System: You are not Joe, fuck off.

    7. Re:Sure... by arth1 · · Score: 1

      Passwords are not authorization.

      Passwords are not treated as user side authorization, and that's the problem. They're treated as authentication, which they are not. I can give you my password, but you don't become me.

      In a saner world, passwords would be treated as the user side authorization, and not as authentication at all.

    8. Re:Sure... by bingoUV · · Score: 1

      There are 2 authorizations here. You and GP are talking about different ones.

      1. GP is talking about what the user is authorized by the service provider to see. E.g. in a group account there are multiple human "users", but only the administrator of the account is authorized by the service provider to see / do certain things.

      2. You are talking about what the human user authorizes the service provider to do. In the more general case, it could be e.g. change the profile picture or see last 25 emails.

      Ok, you have now told that you know the foobarbaz passphrase, but who are you?. It's authorization, because it can be shared. I can authorize someone to act on my behalf. But they don't become me.

      None of it makes sense on the internet.

      Biometrics is like the username. It only tells who you are.

      It only tells who somebody is. You can use somebody else's biometrics as easily or more easily than your own, depending on the situation.

      A password is something you know, and authorizes the action, whether it is you or someone else.

      Authorizing is a process. Password is a noun, a string, and a literal bunch of zeros and ones. Simple dimensional analysis proves that they are not the same. A whole process authorizes the action - which is a meeting of the minds, in some ways.

        Authorization, in the meaning you are using , involves at least :
      1. Service provider feeling a need to do something with your account (could be requested by you).
      2. It correctly communicating to you that it needs to do this particular thing with your account and needs you to authorize it to do so.
      3. You correctly understanding that this particular entry of password by you in the service provider's interface* is for authorizing it to perform that particular action on your account.
      4. You entering the password.
      5. Service provider checking this is your password.

      * Service provider's interface could be anything, even an SMS sent by you to a correct destination, or a sound made by your throat that reaches somewhere the service provider can hear it.

      --
      Bingo Dictionary - Pragmatist, n. A myopic idealist.
    9. Re:Sure... by mencik · · Score: 1

      The password foobarbaz AUTHENTICATES user yadda to the system. What user yadda is AUTHORIZED to do on the system is a totally separate issue. Is user yadda an administrator or a general user? Something else provides that AUTHORIZATION. Please take a Computer Security 101 class and then maybe you will begin to understand the difference.

    10. Re:Sure... by mencik · · Score: 1

      "They're treated as authentication, which they are not. I can give you my password, but you don't become me." Which is why they are lousy authenticators. That is exactly why the push for multi-factor authentication, to make it more difficult for someone to impersonate as someone else. Systems are only authenticating an account when they use a password. They are not authenticating the wetware that is using the account.

  7. Needed it to protect my Bitcoin by Linsaran · · Score: 5, Informative

    About 3 years ago someone stole roughly 2.45 BTC from me.

    The event was a real wake up call for me security wise. They hacked e-mail address to access a password reset form on coinbase and they used social engineering on my cell phone carrier to forward SMS messages (which I used as 2FA on coinbase) to steal that money from me. Ever since then I've had all my 2FA set up through google authenticator instead and 2FA set up on literally everything I can.

    It was only worth about $700 at the time, but now . . .

    --
    In a bit of shameless internet panhandling, I accept Litecoin Donations at Lbd2oH9QsthD1GfuUXPyka12YxvWJYnBVf
    1. Re:Needed it to protect my Bitcoin by Solandri · · Score: 2

      I'd recommend Authy instead of Google Authenticator. It's compatible, but adds a bunch of features like multi-device support, a PC client, and encrypted backup of its database. Most importantly, it simply adds a password. If you have Google Authenticator on your phone and you don't have the lockscreen enabled (or you hand your phone to a friend with it unlocked), anyone who picks up/steals the phone can use your Google Authenticator to login to the accounts it's supposed to be protecting. With Authy, you have to enter a passcode or password to be able to use it. It's free if you use it fewer than 100 times per month. (For enterprise use, try Duo.)

    2. Re:Needed it to protect my Bitcoin by Artemis3 · · Score: 1

      Never leave coins online, period. Run your own wallet with the seed words written manually (not copy pasted or printed) on paper, make a copy of that paper also manually (pen & paper) and store them in different (secure) places, delete the wallet.

      You can still deposit all you want to it. When you want to use the coins, boot a live iso and regenerate the wallet using the words written in the paper and spend the funds, shutdown/reboot afterwards.

      Using a lite wallet like Electrum this process takes no time at all. You can also run a full node/electrum server in your LAN if you want.

      --
      Artix
      Your Linux, your init.
    3. Re:Needed it to protect my Bitcoin by Linsaran · · Score: 2

      I over simplified my above explanation, what I said was technically accurate, but I should mention that they used the hijacked phone account to create an Authy account 'in my name' that Coinbase implicitly trusted even though I had never used Authy with them in the past. I'm not exactly sure why the Authy account was necessary for whatever scheme those assholes were pulling to get into accounts; but the fact that they used it soured me to the service. Not terribly worried about the google auth since I have a lockscreen set up. And if I hand my phone to a friend unlocked and they start trying to steal my account info then I think I have bigger problems.

      Thanks for the suggestion though.

      --
      In a bit of shameless internet panhandling, I accept Litecoin Donations at Lbd2oH9QsthD1GfuUXPyka12YxvWJYnBVf
    4. Re:Needed it to protect my Bitcoin by Linsaran · · Score: 1

      The lion's share of my coins were in my own personal wallet. I don't exactly remember why I had those ones in Coinbase, but it wasn't like I was storing them there, I think I had plans for them, I just don't remember what they were now.

      --
      In a bit of shameless internet panhandling, I accept Litecoin Donations at Lbd2oH9QsthD1GfuUXPyka12YxvWJYnBVf
    5. Re:Needed it to protect my Bitcoin by thegarbz · · Score: 1

      You'll get the last laugh in a few months when it's completely worthless :)

    6. Re:Needed it to protect my Bitcoin by Anonymous Coward · · Score: 0

      Oh, you're one of those morons who regrets not buying any coins and is still too stupid to buy some now.

  8. Security by authority by Anonymous Coward · · Score: 0

    2FA isn't secure if it only relies on a phone number as a substitute for cryptography. A single call to the outsourced customer service department of your phone company could transfer your number to the sim card of a malicious actor.

    1. Re:Security by authority by vux984 · · Score: 2

      "2FA isn't secure if it only relies on a phone number as a substitute for cryptography. A single call to the outsourced customer service department of your phone company could transfer your number to the sim card of a malicious actor."

      So now it requires they know your phone number, and dedicate up to an hour or so of human time, of a human capable of social engineering a telco rep...to transfer a sim. They'll do that for a specific high value target, but not some rando.

      Plus, without 2FA, i've already pwned your account and stolen your bitcoins by the time you read this post. With 2FA, assuming i can even figure out your phone number (not a given), I'll still be on hold with your telco for another 10 minutes before I can even attempt to start social engineering a SIM transfer.

      Your absolutely right... 2FA isn't perfect, especially SMS based 2FA. But its about a million times better than no 2FA at all.

    2. Re:Security by authority by Anonymous Coward · · Score: 0

      Use a TOTP code or U2F device.

  9. For obvious reasons ... by Anonymous Coward · · Score: 2, Interesting

    Less Than 1 in 10 Gmail Users Enable Two-Factor Authentication

    Because I refuse to give Google my cell phone number to text me, because there is no way in hell they need to be able to track me even further.

    That's a big old "hard no" there, chief.

    Google's 2FA is as much about them getting more information about you as it is your security.

    1. Re:For obvious reasons ... by grub · · Score: 2

      You don't need to give then your phone number, you can use the Google Authenticator app to generate the one time pass on your device.

      --
      Trolling is a art,
    2. Re:For obvious reasons ... by tepples · · Score: 2

      You don't need to give then your phone number, you can use the Google Authenticator app to generate the one time pass on your device.

      As I wrote in my reply to DontBeAMoran, you can't set up TOTP until you've set up SMS.

    3. Re:For obvious reasons ... by Obfuscant · · Score: 4, Insightful

      You don't need to give then your phone number, you can use the Google Authenticator app to generate the one time pass on your device.

      Yeah! This! You don' t need to give them your phone number, you can let their app do it for you. Easy peasy.

      The summary comments on only 12% of people "securing" their accounts with a password manager. A password manager doesn't secure your account. It stores passwords. If you have one account and can remember your password, you don' t need a password manager.

      A password manager is actually a one-point-of-failure way for a bad guy to get all your passwords.

    4. Re:For obvious reasons ... by Anonymous Coward · · Score: 0

      You are not even close to reality. There is no texting. at all. If you have an Android phone connected to your gmail account, it's as simple as clicking Yes on the phone when prompted.

      If not, use Google Authenticator.

      This is about securing your account, not collecting information. If you are worried about Google, don't use them. Don't use gmail, but if you are using gmail, there is absolutely no logical or technical reason to not enable 2FA.

    5. Re:For obvious reasons ... by grub · · Score: 1

      It doesn't even need to be their app if you don't trust google. There are many available available, HOTP & TOTP are well documented.

      --
      Trolling is a art,
    6. Re:For obvious reasons ... by grub · · Score: 1

      That's weird, perhaps new? I never have given them my phone number and have been using 2FA with them since they brought it out. I refuse to use any service that requires my phone number, which precludes me from installing many IM-type apps.

      --
      Trolling is a art,
    7. Re:For obvious reasons ... by Anonymous Coward · · Score: 1

      You don't need to give then your phone number, you can use the Google Authenticator app to generate the one time pass on your device.

      This app requires the following permissions:
      Access to your phone book
      Access to storage devices
      Access to your camera
      Access to your microphone
      Access to your call records
      Access to your photos
      Ability to send SMS
      Ability to make calls
      Access to device identifiers
      Access to Internet
      Access to Wifi

      They will get your phone number one way or another. I do not use 2FA because I don't want all these online services to know everything about my private life, which inevitably ends up in some government cesspool so that Joe from the local police station knows what you said on twitter last night.

    8. Re:For obvious reasons ... by swillden · · Score: 4, Informative

      You don't need to give then your phone number, you can use the Google Authenticator app to generate the one time pass on your device.

      This app requires the following permissions:
      Access to your phone book
      Access to storage devices
      Access to your camera
      Access to your microphone
      Access to your call records
      Access to your photos
      Ability to send SMS
      Ability to make calls
      Access to device identifiers
      Access to Internet
      Access to Wifi

      It does not. I don't know if you're deliberately lying or looking at something else but the above is simply false.

      Per the info on Google Play, the Google Authenticator app requires:

      Camera
      - take pictures and videos
      Other
      - create accounts and set passwords
      - full network access
      - control Near Field Communication
      - use accounts on the device
      - control vibration

      Camera is used to grab QR codes. That's the mechanism by which Authenticator is generally configured. I'm not sure what "create accounts and set passwords" means. It has network access to check time. It uses NFC to deliver authentication codes via NFC. It "uses accounts on the device" to see what accounts you have that you might want to set up authentication for. It controls vibration to, well, vibrate.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:For obvious reasons ... by Anonymous Coward · · Score: 0

      Bah. You and your fancy schmantzy password managers. I just store my passwords in plaintext as a gmail draft.

    10. Re:For obvious reasons ... by Anonymous Coward · · Score: 0

      Per the info on Google Play

      If you're running Google Play (or stock android), you've already been exposed by google. No need to quibble about the permissions required by Authenticator.

    11. Re:For obvious reasons ... by Anonymous Coward · · Score: 0

      I don't understand all the fuss over the permissions for this one app. If you are on Android and using Google Services they pretty much have access to your entire phone anyway.

    12. Re:For obvious reasons ... by david_thornley · · Score: 1

      Camera is used to grab QR codes.

      Sure it is. Now, what else is it used for, and how would you figure that out? I really don't like the Android permission system. Given the "full network access", it could turn into an effective spy app within the permissions you quoted.

      --
      "When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
  10. Sounds reasonable by mykepredko · · Score: 1

    I use my gmail account as a spam dump - you want to send me something that I'm not asking for, you get my gmail account. I suspect many other people use it for that as well. Note that this only assumes accounts using the "gmail" domain and not business accounts that are hosted by Google (and are gmail accounts in all but name).

    Next on the list are kids who wouldn't be savvy enough (or have a credit credit/cell phone), then I don't see them using two factor authentication. Then you have companies that create accounts for testing and demonstrations. Finally, you have people who don't think their privacy, information, social security or credit card numbers are important enough to warrant entering a number that comes through on their phones when they log into their GMail accounts. Put them all together and 90% not using two factor authentication seems reasonable.

    For the many people that will disagree with this post, you can voice your concerns via email at myke.predko@gmail.com

    1. Re:Sounds reasonable by Anonymous Coward · · Score: 0

      someone who couldn't get a screen name with the spelling Mike?

    2. Re:Sounds reasonable by Anonymous Coward · · Score: 0

      Or Russian. Maybe he stole Hillary's emails. Seems suspicious.

    3. Re:Sounds reasonable by Anonymous Coward · · Score: 0

      You really think those fringe cases make up 90% of Gmail's base? What you describe might make 0.09%, maybe and that I have doubts of even that much. I'd venture the number of legit Gmail users around 99%+ of Gmail's base.

      We're talking about over a billion users, not a couple 1000

  11. Phone number? SMS? by DontBeAMoran · · Score: 4, Insightful

    Why is everyone talking about cellphone numbers and SMS?

    Aren't we talking about Google's own Authenticator application?

    --
    #DeleteFacebook
    1. Re:Phone number? SMS? by Anonymous Coward · · Score: 0

      Go try using google authenticator app without a phone number linked. See how far you get :-)

    2. Re:Phone number? SMS? by bluefoxlucid · · Score: 3, Insightful

      You can use a FIDO U2F device, too.

      I have 2FA on. I'm a Congressional Candidate with a technology background; if I got hacked for not taking basic security countermeasures, I'd drop out of the race.

    3. Re:Phone number? SMS? by grub · · Score: 1

      Someone mentioned that before, but I've never given them my phone number. Have used it since they brought it out.

      --
      Trolling is a art,
    4. Re:Phone number? SMS? by DontBeAMoran · · Score: 1

      I've got about six websites linked to it, never had a phone number/phone service on my old iPhone. That's how far I got.

      --
      #DeleteFacebook
    5. Re:Phone number? SMS? by Anonymous Coward · · Score: 0

      I have no idea what a Google Authenticator App is, let alone how it works, or what FIDO is or U2F. None of those things make sense, so why in the world would I ever use them?

      "Do a search" the lazy nerd would say. Except that doesn't apply to people who have never heard of those things. It's just like website authentication certificates, or electronic signatures or PGPs. Ordinary people don't even know what their purpose is, let alone how they work, so only the enthusiastic geeks use them. I thought computers were supposed to make life easier, instead we waste so much time managing the computers.

    6. Re:Phone number? SMS? by Anonymous Coward · · Score: 0

      I have a similar experience in which Google's online UX demands that I add a phone number to my account for "account recovery" before I would be allowed to enable two factor authentication. As I read the documents, they want to force this recovery mechanism to be enabled before they will allow two-factor. I am sure they are trying to cut down on support costs when people lock themselves out. I see this same conceptual flaw with a number of websites, including banks and investment firms.

      They seem profoundly confused about what two factor means, if they think that adding a cell phone as a new single factor option (for "recovery") is adding security. It's complete security theater, since authentication is only as strong as the WEAKEST option that is allowed. It's like upgrading your dead-bolt with a two-stage man-trap, but at the same time adding a rope ladder to the back window in case you lock yourself out.

      There should be an "I really mean it" option which requires submitting in person with legal identification whenever you want to bind/recover authentication tokens with an account. Do it in partnership with networks of banks or other firms with distributed brick and mortar locations where people can appear and be authenticated in person by someone with training at least equivalent to a notary public.

    7. Re:Phone number? SMS? by Anonymous Coward · · Score: 0

      #justicedemocrats

    8. Re:Phone number? SMS? by swillden · · Score: 2

      I have no idea what a Google Authenticator App is, let alone how it works, or what FIDO is or U2F. None of those things make sense, so why in the world would I ever use them?

      "Do a search" the lazy nerd would say.

      I'm a lazy nerd and that's not what I would say. I would say: "Go to myaccount.google.com and click on 'Signing in to Google'. It explains all of the options."

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:Phone number? SMS? by sexconker · · Score: 1

      And you set it up before they instituted this requirement.

      Go turn it off, then try turning it back on again.

    10. Re:Phone number? SMS? by DontBeAMoran · · Score: 1

      Go turn it off, then try turning it back on again."

      Do you work in IT?

      --
      #DeleteFacebook
  12. Cost per received message by tepples · · Score: 2

    The main reason that I haven't enabled 2-factor on my account is that U.S. cellular carriers charge not only for sent messages but also for received messages. T-Mobile, for example, charges its pay-as-you-go customers 10 cents to send and 10 cents to receive. And no, Google and Twitter don't allow use of a FIDO U2F key or a TOTP client without also having a mobile phone number set up.

    1. Re:Cost per received message by murdocj · · Score: 1

      I pay $35/month and that includes unlimited USA talk and text with my limited data. Maybe you need to get another carrier. Or at least another plan.

    2. Re:Cost per received message by Anonymous Coward · · Score: 1

      You have to add a mobile number to set up FIDO U2F key or a TOTP client but you can just remove it right after. IDK why they do it that way.

    3. Re:Cost per received message by tepples · · Score: 2

      I pay $35/month and that includes unlimited USA talk and text with my limited data. Maybe you need to get another carrier. Or at least another plan.

      I currently pay $3 per month to T-Mobile and get 30 minutes of USA talk, 30 USA texts, or a combination thereof per month, and zero cellular data. Thus the price difference between my pay-as-you-go plan and your unlimited plan is $32 per month or $384 per year. I'm interested to read a good case for how 2FA would be worth that much to me.

    4. Re:Cost per received message by torkus · · Score: 2

      Exactly how many times are you going to point out the SMS requirement to set up TOTP in a /. posting?

      SMS also provides a fallback if your auth token goes poof...and if you're a PAYG cell user and want the security then you spend the 10c on an SMS or two.

      BESIDES all that...google already knows your phone number if you use their services. Guaranteed. It's extremely unlikely they haven't parsed it from one of your emails, order receipts, account setup forms, signature lines, etc. already...or that of someone else you're associated with. Stamping your feet and 'refusing' to give that info up is as childish as it is pointless.

      Or, ya know, don't use a free TOTP on a free email service. Go pay for something that suits your particular needs.

      --
      You can get rich if you own a politician, but you have to be rich to buy one in the first place.
    5. Re:Cost per received message by torkus · · Score: 1

      Nah, it's just a straw man and proof that someone will always find fault no matter what is done.

      --
      You can get rich if you own a politician, but you have to be rich to buy one in the first place.
    6. Re:Cost per received message by Anonymous Coward · · Score: 0

      Or another Webmail provider. Google is being an ass here. If they really want to support as much 2FA as possible, they should except FIDO U2F (or equivalent) without the SMS/Voice BS. The notion that you're supposed to just get a better mobile plan is insane just to use (or enable) FIDO U2F.

    7. Re:Cost per received message by tepples · · Score: 1

      SMS also provides a fallback if your auth token goes poof...and if you're a PAYG cell user and want the security then you spend the 10c on an SMS or two.

      Is that 10 cents just to set it up, or is it also 10 cents every time I log in?

    8. Re:Cost per received message by murdocj · · Score: 1

      You said you weren't using two factor auth because you were paying ten cents per text. Which implied that no extra cost for text would be worth it to you.

    9. Re:Cost per received message by Anonymous Coward · · Score: 0

      BESIDES all that...google already knows your phone number if you use their services.

      Fun fact: Gmail didn't always require you to provide a phone number to use their service. That's a good thing since I don't have a cell phone. I also don't see the point in giving Google my land line number. It'd be more effective to disable the ability to use a phone number/sms with the account to make it impossible for someone else to social engineer a way into the account. You know, like how people prefer having a credit freeze over some bullshit where you just pray someone can't trick a random creditor to accept fraudulent info and fuck you over?

      Or, ya know, don't use a free TOTP on a free email service. Go pay for something that suits your particular needs.

      Exactly this. So, we can agree Google doesn't really provide good TOTP service. Which explains why 82% of people (in a rather informal survey) correctly guessed less than 10% of people use 2FA with Gmail. Clearly Google doesn't just not care about 2FA, it's made itself clearly hostile enough that a vast majority of people realize it.

    10. Re:Cost per received message by Anonymous Coward · · Score: 0

      Maybe you need to get another carrier. Or at least another plan.

      For people who don't use mobile phones a great deal PAYG is often way cheaper than a contract.
      Stop assuming everyone is a phone junkie.

    11. Re:Cost per received message by gaiageek · · Score: 1

      Look into Truphone prepaid SIM.

    12. Re:Cost per received message by Anonymous Coward · · Score: 0

      Who the hell pays for texts in 2018? You are a whip and buggy salesman's wet dream.

    13. Re:Cost per received message by tepples · · Score: 1

      It'd change from 10 cents for the first text and 10 cents for each additional text to $32 for the first text and 0 cents for each additional text. I'd have to send or receive 320 texts, minutes, or a combination thereof each month in order for that to be a win. Currently I do not.

    14. Re:Cost per received message by tepples · · Score: 1

      Who the hell pays for texts in 2018?

      Someone who cut his phone bill by over a hundred dollars a year by downgrading from an unlimited plan to a pay-as-you-go plan.

    15. Re:Cost per received message by bluefoxlucid · · Score: 1

      I pay under $15/month with unlimited voice and text, and 2G LTE+ data, with unlimited throttled data after that.

    16. Re:Cost per received message by bluefoxlucid · · Score: 1

      Generally, Google lets you log in and remember the machine logging in for 30 days before re-authenticating. TOTP uses a shared secret, so you already have the data on your device and can enter it in without them sending you anything.

    17. Re:Cost per received message by Anonymous Coward · · Score: 0

      I pay $35/month and that includes unlimited USA talk and text with my limited data. Maybe you need to get another carrier. Or at least another plan.

      I currently pay $3 per month to T-Mobile and get 30 minutes of USA talk, 30 USA texts, or a combination thereof per month, and zero cellular data. Thus the price difference between my pay-as-you-go plan and your unlimited plan is $32 per month or $384 per year. I'm interested to read a good case for how 2FA would be worth that much to me.

      A mobile device is the general requirement for many 2FA solutions, unless you're willing to pay a lot more for a dedicated token device and service.

      Instead of trying to justify a $384 price increase for 2FA, you should be looking at why you even own a mobile device. Your plan is cheap, but effectively worthless for anything other than a rare quick phone call or text message, and if it's actually a smartphone, then it's a waste of resources altogether. If you carry a device for emergencies only, then go find a used deactivated phone and reduce that $3/month to zero. 911 still works whether a plan is active on a device or not.

    18. Re:Cost per received message by grub · · Score: 1


      Fun fact: Gmail didn't always require you to provide a phone number to use their service.

      Exactly right. I never did give them my phone number 'way back' and was surprised reading all these comments that say they now require it.

      --
      Trolling is a art,
    19. Re:Cost per received message by Anonymous Coward · · Score: 0

      Anyone who pays for OOB data that towers hand off for free truly needs their mind examined more than President Trump.

    20. Re:Cost per received message by Anonymous Coward · · Score: 0

      unless you're willing to pay a lot more for a dedicated token device and service.

      FIDO U2F Security Key is only $18 and there are cheaper/different vendors. Admittedly, that amounts to 180 10c text messages, so one could argue that text messages would likely be cheaper. And his plan already covers 30 texts which might cover his actual usage pattern. Regardless, a one time fee for $18 dongle is not "a lot more" than $32/month extra. In the end, it makes no sense to require SMS or Voice for the purpose of 2FA; it's not even the best type of 2FA. Clearly the point is to tie an account to a phone number which hopefully is a unique person.

    21. Re:Cost per received message by blind+biker · · Score: 1

      The main reason that I haven't enabled 2-factor on my account is that U.S. cellular carriers charge not only for sent messages but also for received messages.

      Planet USA. You know, I am not anti-Trump and I also don't support all the crap the EU Commission is spewing (in fact, fuck the EU Commission - bunch of unelected bureaucrats), but you guys really do things weirdly. No universal healthcare? Not enough competing ISPs so you have some of the highest rates in the western world? Workers can be fired for no reason? And you have to pay for received SMS?? That sounds like crazy stuff to me.

      --
      "The agriculture ministry is not in charge of Gundam" - Japanese ministry official.
    22. Re:Cost per received message by Anonymous Coward · · Score: 0

      SMS also provides a fallback if your auth token goes poof...

      Do you realize how ridiculous that is? Weaker authentication method can bypass stronger one. What is the point of 2FA if you can bypass it via social engineering (SMS redirect)?

    23. Re:Cost per received message by Anubis+IV · · Score: 1

      And no, Google and Twitter don't allow use of a FIDO U2F key or a TOTP client without also having a mobile phone number set up.

      You sure about that? I know that used to be the case, but I'm not sure that it still is. I don't have a phone number set up on my Google account, yet I'm using TOTP. I suppose it's possible that I deleted it from my profile after I set up 2FA, but I don't recall doing so.

    24. Re:Cost per received message by tepples · · Score: 1

      Which carrier might that happen to be?

    25. Re:Cost per received message by tepples · · Score: 1

      the price difference between my pay-as-you-go plan and your unlimited plan is $32 per month or $384 per year. I'm interested to read a good case for how 2FA would be worth that much to me.

      Penny wise and pound foolish I would say....

      Through this cliche', I assume you are claiming that 2FA is in fact worth the price of receiving a text message every time you log in. I'm interested to read details of your reasoning beyond just this cliche'.

    26. Re:Cost per received message by Anonymous Coward · · Score: 0

      I'm not who you were replying to but I was curious so I looked around. I found some plans similar to your current one (but better?) as well as his.

      TextNow:
      $2.99/mo: unlimited calling and texting, no cellular data
      $19.99/mo: unlimited calling and texting, 1.5 GB cellular data then unlimited data at 2G speeds

      FreedomPop:
      Free: 200 minutes, 500 text messages, 500 MB data (CDMA) or 200 MB data (GSM)
      $10.99/mo: unlimited text and talk, 500 MB data
      $24.99/mo: unlimited text and talk, 2 GB data
      $9.99/mo prepaid for 12 months: unlimited text and talk, 2 GB data

      I'm not necessarily recommending them (I have no experience with either and I haven't looked into either company in depth), I just thought they might be of interest to you. There are downsides to cellular resellers (MVNOs). Some of them are ad-sponsored (maybe avoidable if you can bring your own phone), many haven't been around long, most don't use AT&T or Verizon's towers so they have worse reception outside cities, not all offer 4G data and when they do it might be throttled, and many MVNOs just seem kind of sketchy.

      But if they fit your needs they can save you hundreds every year.

    27. Re:Cost per received message by thegarbz · · Score: 1

      The main reason that I haven't enabled 2-factor on my account is that U.S. cellular carriers charge not only for sent messages but also for received messages.

      Wow I feel like I just timetravelled to the 90s!

    28. Re:Cost per received message by bluefoxlucid · · Score: 1

      MintSim, on T-Mobile's network. It's currently an upfront $180/month plus 3% taxes and regulatory fees, so about $5.4 of fees for the year. T-Mobile and Ting were charging me like $7-$11 each month for taxes and fees! I'm down from as $828/year bill with 2G of LTE.

      They have a 3 month promotion for $45 to lure in new customers. It's $300/year for 10GB of LTE data per month, but who needs it?

  13. Password Managers by Anonymous Coward · · Score: 1

    Part of the problem with password managers is that the reviews are so poorly written. I have looked for: free, easy to use, cross-platform. Yes, of course I have googled it. I still cannot find one that is good enough to recommend to my students.

    1. Re:Password Managers by Hal_Porter · · Score: 1

      I use the SirPwnAlot password manager. It comes with the SirPwnAlot browser toolbar which is free. In fact you may already have installed it - it's bundled with a lot of software.

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    2. Re:Password Managers by Moritz+Moeller+-+Her · · Score: 1

      I recommend bitwarden - works like Lastpass, only free and even free software and you can run your own servers if you want.

      --
      Moritz
  14. Hmm by Anonymous Coward · · Score: 0

    I just did this for shits and giggles.. upon typing in my cellphone number, my username temporarily changed to a gmail account I deleted 6 years ago.

  15. Two-factor As Implemented Won't Work For Some Uses by sehlat · · Score: 1

    For example, when two people need (legitimate and approved) access to the same email account in order to receive confirmation codes from, say, our bank. The authenticators have to be set up simultaneously on two devices (one per person) and have to STAY in sync. If my wife's phone runs out of charge (this has happened), you have to go through the whole resync process again. I won't say it's a pain in the neck. I have a much lower opinion of it than that. I tossed two-factor out.

    When Google sets up some method whereby two-factor can be (verifiably approved) so that two people can conveniently share an account. I'll be interested. But not until then.

  16. Must use SMS to set up TOTP by tepples · · Score: 3, Informative

    You are correct that Google publishes a TOTP client called Google Authenticator. But when I installed Google Authenticator, I discovered that Google is unwilling to offer TOTP authentication unless the account holder has already linked a phone on a supported carrier. From "Install Google Authenticator":

    To set this up, first you need to complete SMS/Voice setup. Then, follow the directions for your type of device explained below.

    1. Re:Must use SMS to set up TOTP by DontBeAMoran · · Score: 1

      That's weird, I never had phone service on my old iPhone and their authenticator works fine.

      --
      #DeleteFacebook
    2. Re:Must use SMS to set up TOTP by Anonymous Coward · · Score: 0

      That's not correct. The article you linked to is for people that want to use SMS or a voice call for two factor. Not only can you use the Google Authenticator app without SMS you can also use the Google Search app to just get a yes/no prompt when you try to login from an unknown device. Besides the insecurity of SMS I don't have an SMS plan and am charged twenty cents per text. I'm 100% positive I never used my cell phone number when setting up Google Two Factor auth.

      https://support.google.com/accounts/answer/7026266?co=GENIE.Platform%3DiOS&hl=en

    3. Re:Must use SMS to set up TOTP by AmiMoJo · · Score: 1

      I use the Google Authenticator app and did not need to add my phone or accept any SMS messages to make it work. I simply scanned a QR code off the screen.

      I think that text might be out of date.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    4. Re:Must use SMS to set up TOTP by sexconker · · Score: 2

      When I had to re-set up Google Authenticator for my Google account last February (due to my prior phone bricking itself), I was forced by Google to give them my phone number for an SMS message / voice call in order to set up the authenticator app.

    5. Re:Must use SMS to set up TOTP by Anonymous Coward · · Score: 0

      I have Authenticator installed and working on a tablet with no cellular capability.

  17. Re:Two-factor As Implemented Won't Work For Some U by Anonymous Coward · · Score: 0

    what are you bitching about - you just set up the authenticator using the same secret. it works fine. i have two devices which can authenticate (my phone and a backup).

  18. 10% is a lot by Anonymous Coward · · Score: 0

    "but virtually no one is using it"

    10% of 1 billion (https://www.statista.com/statistics/432390/active-gmail-users/) is 100 million people are using it, which I think is a lot of people, it's more than say the population of the UK.

    It's also not a bullet proof solution, texting the code can be intercepted by anybody with the right equipment and location for example.

    Having a randomly generated password which you change every 30 days, might well be stronger, and nothing stops governments or other authorised authorities from requesting the contents.

    If you don't want you somebody else to read an email, use GPG/PGP solutions would be recommended and gives much better security, as the encryption is done on a per recipient basis, this is much more secure.

    I think 100 million is a good start, but google could do more to make it easier and prompt people when they login.

  19. I used to, then stopped by Anonymous Coward · · Score: 5, Interesting

    I had 2FA enabled, then left my phone in an uber by accident and a subsequent passenger stole it. The emergency 2FA codes I'd printed out didn't work. In order to track and remotely disable my phone, I ended up having to use a computer which I'd thankfully left logged into gmail to disable 2FA for my account (which for some reason it allowed me to do without any 2FA code), after which I could do what needed doing. I haven't re-enabled it since because I realized that losing or breaking my phone is frankly more likely than having my password stolen, and losing my phone with 2FA enabled can be a disaster of its own (even if emergency codes work, what if I don't have them with me? And if I need to carry them with me whenever I stray more than an hour or so from home, that makes it much more likely that the emergency codes themselves could be lost or stolen.) As I learned after that incident, any other services you've tied into Google Authenticator 2FA also become a huge hassle to regain access to, because just installing Google Authenticator on your replacement phone won't cut it.

    1. Re:I used to, then stopped by Anonymous Coward · · Score: 0

      I ended up having to use a computer which I'd thankfully left logged into gmail to disable 2FA for my account (which for some reason it allowed me to do without any 2FA code), after which I could do what needed doing.

      This.

      I'm an IMAP-based gmail user on the desktop. The browser almost never has a Google account logged in to anything. (I'm sure Google correlates the IP of the successful IMAP with my search data, but that's not relevant for purposes of this discussion.)

      The problem with 2FA is that the most likely thing to get compromised while logged in to my Google account is (duh!) the mobile phone, which is unfortunately often the second factor in 2FA.

      In a scenario in which the phone is stolen, by the time I get back to the desktop machine, how the hell am I supposed to log in to the google account now that the attacker - who has physical posession of the phone and the second factor of its phone number and ability to receive SMS - and change the password?

    2. Re:I used to, then stopped by swillden · · Score: 2

      Add some more 2FA options.

      Google allows you to set up a FIDO security token AND the Authenticator app AND one or text/voice numbers AND a set of backup codes, any one of which will get you in. With enough different options, you'll never be locked out.

      I use all of the above. There is a caveat on the text/voice numbers, which is that attackers have been able to hijack cell numbers, so consider that carefully... but if you also have a good password you've significantly raised the bar for anyone to hijack your account if they have to both steal your password (which you never use anywhere else, and never enter into any form that isn't on a Google site, right?) and hijack your cell. It's also a good idea to test your backup codes periodically, though I've never had mine fail to work.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    3. Re:I used to, then stopped by ugen · · Score: 1

      And don't forget that there is no way to transfer authentication credentials from one device to another (as I just found out). So, if you have to change a phone, you will need to visit every single service that is using Google Authenticator and reconfigure it to use a new device, from the beginning.

      Also - it appears to only allow a single authenticator at a time. I like my phone, but I am not quite that married to it and I do need to access various services sometimes where my phone is not available or not convenient to access.

    4. Re:I used to, then stopped by WinstonWolfIT · · Score: 1

      Isn't this just a case of using multiple methods to 2fa? I've taken some care in this regard, down to in some cases recovery codes on a thumb drive. I've bricked a notebook and changed sims (which is harsher than a lost phone) and recovered completely in both instances.

    5. Re:I used to, then stopped by Anonymous Coward · · Score: 0

      wtf is a FIDO security token, and why in the world would you expect Joe and Jane Gmailuser to know what that is and how it works and use it?

      I googled FIDO and all of the returned results are for a Canadian cell phone company or a 10-year-old Canadian movie. I'm not Canadian.

    6. Re:I used to, then stopped by Dragonslicer · · Score: 1

      And don't forget that there is no way to transfer authentication credentials from one device to another (as I just found out).

      Just enter the same seed and you'll get the same codes.

    7. Re:I used to, then stopped by Anonymous Coward · · Score: 0

      "No way to transfer" is incorrect. Authy can back up the codes and import them to new devices, it also allows you to use them on multiple devices at once. Google Authenticator is super bare bones, and not the best out there. The only reason to use it is for U2F on an Android phone (Google Authenticator is required for U2F over NFC).

      Google allows multiple 2FA methods at once, so you could use TOTP codes or a FIDO U2F device.

    8. Re:I used to, then stopped by swillden · · Score: 1

      Go to myaccount.google.com. Google's documentation explains all this.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
    9. Re:I used to, then stopped by Anonymous Coward · · Score: 0

      The emergency 2FA codes I'd printed out didn't work.

      wtf? Did you find out why?

      I disabled all weak authentication methods on mail Google account, i.e. removed cell phone number from profile.
      I am relying on the fact that 10 emergency codes work if my phone with 2FA gets lost.

    10. Re:I used to, then stopped by Anonymous Coward · · Score: 1

      No, never did find out why. You may want to occasionally try one of your emergency codes, and generate a new set if it doesn't work.

    11. Re:I used to, then stopped by Anonymous Coward · · Score: 0

      I had recovery codes, but Google didn't accept them. And I had to change SIM after losing the phone, since obviously I lost the SIM with it.

  20. The reason by Anonymous Coward · · Score: 0

    few are using TFA for gmail is because no one really uses gmail for much of anything.

  21. obligatory Game of Thrones callback by stereoroid · · Score: 3, Informative

    "Fewer."

    --
    (this is not a .sig)
    1. Re:obligatory Game of Thrones callback by mujadaddy · · Score: 0

      This is an underrated comment.

      --
      Populus vult decipi, ergo decipiatur...
      "Force shits upon Reason's back." - Poor Richard's Almanac
    2. Re:obligatory Game of Thrones callback by Godwin+O'Hitler · · Score: 1

      "Hypercorrection."

      --
      No, your children are not the special ones. Nor are your pets.
  22. Everyone Leads a Boring Life by Anonymous Coward · · Score: 2, Interesting

    Everyone thinks their secret box is more important than their neighbor's secret box.

    Guess what, all your emails are boring! I've been an SA since the 1990s and root on thousands of Unix servers dating back to SunOS-4, and no one has anything interesting in their emails.

    Stop inflating your egos by thinking everyone is after your special sauce. Unless you're connected to a politician or celebrity, no one gives the fattest rats posterior what you gotta say or what you're sending plaintext.

    1. Re:Everyone Leads a Boring Life by Anonymous Coward · · Score: 0

      Except this is 2018 and people link their email accounts to online banking and credit card accounts.

      If you still think like an SA from the 1990s, I sincerely hope that you've retired.

  23. My primary use of email by thinkwaitfast · · Score: 1

    is to remind my girlfriend to buy dogfood when we're out. Good luck to anyone who steals access.

    1. Re:My primary use of email by Ksevio · · Score: 2

      Well guess what? I'm going to hack your email and you'll be getting dogfood WHEN YOU STILL HAVE SOME! AHAHAHAHA

  24. Re:Two-factor As Implemented Won't Work For Some U by sehlat · · Score: 1

    What I'm bitching about is if ANYTHING happens to either of the two devices, you have to go to a fair amount of trouble to reinitialize the synchronization of the Google apps. My wife's phone does NOT live a sheltered life and has gone down on more than one occasion.

  25. Depends on your organization by grilled-cheese · · Score: 1

    If you're using Google Apps on a domain with a delegated SSO, MFA may not be an option for you.

    1. Re:Depends on your organization by Anonymous Coward · · Score: 0

      Correct. Then your org should implement 2FA on their SSO solution.

    2. Re:Depends on your organization by grilled-cheese · · Score: 1

      I was pointing out that the statistics are skewed if you don't exclude SSO gmail users, since that's out of the user's control.

  26. Please!!! Think of the children!!!! by Anonymous Coward · · Score: 0

    Won't someone pleeeeease!!!!!

    Fap fap fap fap fap fap fap fap fap!!!!!

  27. Well, Google mail users. by Anonymous Coward · · Score: 1

    Whoever chooses to use gmail isn't very serious about privacy anyway.

  28. Non-standard Devices by kackle · · Score: 1

    I hope they realize that some of us use many of these accounts with non-standard, human-less devices that aren't PCs, tablets, nor cellular phones.

    1. Re:Non-standard Devices by Anonymous Coward · · Score: 0

      They do. You can generate a unique, static password for that situation and still use 2FA.

  29. Re:Two-factor As Implemented Won't Work For Some U by torkus · · Score: 1

    You might want to look up what TOTP actually stands for. Hint: the first word is Time.

    You can configure as many devices with the same seed as you like. Your wife simply needed to turn her phone back on and give it a moment to sync time with the cell network.

    --
    You can get rich if you own a politician, but you have to be rich to buy one in the first place.
  30. Removing mobile number also removes TOTP by tepples · · Score: 1

    You have to add a mobile number to set up FIDO U2F key or a TOTP client but you can just remove it right after. IDK why they do it that way.

    Last I checked, removing your mobile number from your account had the side effect of also removing FIDO U2F or TOTP from your account. At least Twitter does that. From "Twitter's 2-factor authentication has a serious problem" by Jack Morse:

    What about just deleting your phone number from your Twitter account? Then it can't send you texts, right? Go ahead, but then you can no longer use the 3rd-party authenticator app.

    Does Google also disable TOTP access after you have removed your phone number?

  31. 2FA is too fragile by RightwingNutjob · · Score: 1

    The 2FA at my employer uses a text message to give me a code that I can then use to VPN in. That's great. Except when my phone doesn't get reception. Or when I'm working in a room where carrying wireless devices isn't permitted. Or if I forget to bring my phone with me. Security isn't for free.

  32. 2FA Offers Limited Additional Security by Luthair · · Score: 1

    If you are using a random unique password per site, then the additional protection offered by 2FA is effectively zero.

    With a password that is not re-used, there are two possible attacks (1) phishing, (2) malware. If you are tricked into entering your password on a phishing site then you will almost certainly be tricked into entering your 2FA. If you have malware it can jack your session anyway.

    1. Re:2FA Offers Limited Additional Security by Anonymous Coward · · Score: 0

      "Entering your 2FA" doesn't necessarily give permanent access. If it's time based, it changes and they lose access. If it's based on U2F, your device is authenticating the requestor will not provide the correct response to a third party for them to get into your account.

    2. Re:2FA Offers Limited Additional Security by Luthair · · Score: 1

      They can just remove 2fa from your account with the session.

  33. Re:Two-factor As Implemented Won't Work For Some U by Anonymous Coward · · Score: 0

    Set your wife and you up with your own accounts (and your own 2FA Authenticators). Then you can delegate access to your inboxes to each other if you want to share everything or set-up a third shared account that you delegate out and never bother to log into.

    Or... use Authy as your authenticator app as it will let you sync to multiple devices. It's a less secure, but better than not using 2FA at all.

  34. 2FA usability sucks by juancn · · Score: 2

    Passwords are bad, but are a lot less annoying than passwords plus 2FA. The loss of the second factor is basically a nightmare, and each service wants you to use their own app or whatever. Even changing phones becomes a hassle. I get it for an enterprise environment, where in an emergency, you can call your local IT guy an get them to reset it for you, but if something goes wrong with Google you're screwed. You can't even pay to talk to someone to get it fixed.

    1. Re:2FA usability sucks by u801e · · Score: 1

      Passwords are bad, but are a lot less annoying than passwords plus 2FA.

      If websites would support the client side TLS certificate for authentication, then you could get 2FA by combining that with a username and password. Browsers have natively supported it for decades.

  35. Buy your own email by DogDude · · Score: 1

    This is a moot point if you buy your own email. If somebody gets your password, change it yourself. Or, enable 2 factor authorization, and don't give Google your cell phone number. Email costs $2/month.

    --
    I don't respond to AC's.
  36. It's all about protecting your stuff by Guyle · · Score: 1

    The way I see it, it's not a question of what information you do or do not give Google. If you choose to use their service, then you're agreeing to their terms, and part of those terms is the information they collect. Don't like it? Find another email provider who doesn't collect any infomation. If you're really serious about security, open your wallet and get your own email through a private provider, or stand up your own server that you can secure however you want and thus can be assured your data is safe. The discussion of whether or not to use 2FA is completely separate from that.

    I've used Google Authenticator to secure my Google account for a long time. When Google rolled out the advanced security option, I signed up as soon as I had FIDO keys in my possession. Why? Because your email is the gateway to everything else. Someone who gets access to your email can then get access to other accounts tied to that email address simply by going to the website and hitting "reset my password". Your concern should be making sure that someone can NOT accomplish that by having the ability to hack your shit remotely, and that's where 2FA can really help you.

  37. No cellphone access, no 2FA by mencik · · Score: 2

    Since I cannot have a cellphone in the office, no 2FA for gmail for me.

  38. Re:Two-factor As Implemented Won't Work For Some U by The+MAZZTer · · Score: 1

    Two devices can stay in sync using the current date and time. If your bank couldn't figure out how to resync using that obvious mechanism I don't know what to tell you; every single authenticator app I've seen uses it.

  39. Re:Two-factor As Implemented Won't Work For Some U by The+MAZZTer · · Score: 1

    The synchronization should be handled by the device's clock. Either your wife's phone does not work properly with such a basic feature (which is required for 2FA to work in the first place) or your bank has no idea how to properly handle 2FA security. If I were you I'd be worried about how they handle other types of security.

  40. Robocalls Lost phone by Anonymous Coward · · Score: 0

    Two reasons:
    1) robocalls; how do I know google won't share my phone number with the world?
    2) if I lose my phone how do I access email?

    I would like to use some sort of two-factor identification, but how does one get around these two problems?

  41. No mobile by Roger+W+Moore · · Score: 1

    It doesn't make any difference if you don't own a mobile.

  42. No more "waste of resources" than an iPod by tepples · · Score: 1

    [A pay-as-you-go plan] is cheap, but effectively worthless for anything other than a rare quick phone call or text message

    I use it for exactly that. Longer voice calls wait until I arrive at home, where we have a phone on a different plan with unlimited minutes and zero texts. Longer text conversations wait until I arrive at home or at a hotspot, where I use Internet-based text chat or email.

    and if it's actually a smartphone, then it's a waste of resources altogether.

    I disagree. Even without cellular data, my Android phone is no more "a waste of resources" than an iPod touch. On this 5-inch tablet, I can still access locally stored information anywhere and connect to the Internet at any hotspot.

    If you carry a device for emergencies only

    I carry it not only for emergencies but also for the sort of urgencies for which one would have used a payphone in previous decades. The most common is calling home to arrange a ride after the city buses have stopped running for the night or for the weekend.

  43. Don't need to give them more info by Solandri · · Score: 4, Informative

    Your 2FA can be via mobile phone (SMS), another email account, the Google Authenticator app (though I'd recommend Authy instead), or a pre-generated set of recovery keys you can store on your computer (or write down on a post-it and stick it to your monitor if you wish). The latter two don't require giving up any personal info, and are arguably more secure anyway.

    1. Re:Don't need to give them more info by Anonymous Coward · · Score: 0

      Google also supports U2F devices, such as the Yubikey. NFC or Bluetooth versions work with mobile.

  44. I Don't Always Have My Phone Handy by hduff · · Score: 2

    The concept is great, but if I accidentally left my phone at home, I'm locked out of my email.

    --
    "I believe in Karma. That means I can do bad things to people all day long and I assume they deserve it." : Dogbert
    1. Re:I Don't Always Have My Phone Handy by Anonymous Coward · · Score: 0

      You can get a USB key fob that works as a second factor and lives on your keychain. I guess if you lose your phone, keys, and wallet you might be screwed.

  45. Does not follow by SuperKendall · · Score: 1

    So getting all your email isn't a concern

    Here I assume you mean someone ELSE getting my email? Honestly that is less of a concern to me than Google having more information on me, yes.

    That said Google already has my phone number through lots of other means so I',m not sure I care that much. Still have not turned on two-factor because I use secure passwords (yes I know two-factor would still be better). One impediment is having to re-enter passwords across several devices after I switch over.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  46. Attempted it, Disabled it by Anonymous Coward · · Score: 0

    Their 2FA system demanded a cellphone to work, then failed to make use of the authenticator once a device was set up to access gmail. Since cellphones basically dont have their vulnerabilities patched and it doesnt really use 2FA anyway, 2FA merely added an extra point of failure.... So why bother?

    So far as I am concerened, if I lose or break the authenticator, I'd rather simply have a nuked account to replace than something which can be broken into by a thief using whatever self-defeat they build into the system to keep people who lose their own credentials happy.

  47. I use Gphone for 2FA by 140Mandak262Jamuna · · Score: 1
    For some reason not all the authentication SMS comes through in my T-Mobile phone. Some banks and brokerages send the authentication from a five digit cell phone number, and t-mobile filters them out based on some seemingly random algorithm.

    So I switched them all to Google Phone number. In my google phone account I set up the SMS to echo to gmail. The gmail account also uses 2FA but these are my desktops at home and work, and one chromebook at home. So even if I lose my phone, I have my desktops to get the authentication codes.

    --
    sed -e 's/Chuck Norris/Rajnikant/g' joke > fact
  48. Because it's not worth it... by Anonymous Coward · · Score: 0

    There is nothing in my GMail account worth the trouble. GMail is just for throwaway accounts. They are one micro-step above Mailinator in the grand heirarchy of email account value. For $10 a month to host my own domain and email, it's just not worth using those turkeys.

  49. Used it, hated it by ArhcAngel · · Score: 1

    I tried Google's two factor for about six months. It was a PITA! The app would randomly stop working and when I was on another device It would make me jump through nigh infinite hoops to log me in. If the pain exceeds the user''s threshold they aren't going to use it unless they have to. I turned it off and have never tried it since. Most users have less patience than I do so 1 in 10 sounds about right.

    --
    "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
  50. Too Many Passwords by Anonymous Coward · · Score: 0

    The problem is that we have too many passwords, too many accounts, too many things to bloody remember.

  51. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  52. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  53. Ignore this fuckwit by Anonymous Coward · · Score: 0

    Bullshit. No matter who you are and how unimportant you are, two things will still apply:

    1) Your money is just as good as anyone else's. If I could steal $10 from your wallet, I wouldn't stop and think, "wait, maybe I should steal $10 from Jeff Bezos instead. I'll go look for him." Bzzt. Your $10 will do just fine.

    2) Regardless of how much or little your adversary values what they get from you (maybe the above fuckwit is right that they might not value it at all), you will negatively value the loss. It sucks to be a victim, even if it also sucks to be the thief. ;-) If Jeff Bezos steals $10 from you, maybe that's not a great windfall to him, but to you, ten bucks is still ten bucks.

    Guess what, all your emails are boring!

    And you determine that, by reading them. And finally, the Grand Fuckwittery that proves the above poster is a very special idiot:

    Stop inflating your egos by thinking everyone is after your special sauce.

    It's not about "everyone" it's about "anyone" or "anything" since the attacker is probably an unconscious script. And the robot isn't after your special sauce specifically, it's after whatever the hell it can get.

    Shit, I'm not done yet. Just when I think I have identified all the stupidity, I keep finding more:

    Unless you're connected to a politician or celebrity

    So.. maybe about one in ten people? There are an awful lot of politicians and celebrities, and especially the politicians mix quite a bit. Anyone who wants to, can trivially "get connected" to a politician. If you haven't done it, it means you haven't tried. You don't even need much money; $100 will do. I'm not saying that'll get you their dick pics, but it might!

  54. 2FA is a PITA by MobyDisk · · Score: 1

    2FA has made me stop using my Google account. I previously used it for some Google groups. But now when I get an email saying that there is a new message there, I click the link to read it, and then give-up because I have to do some process that involves a text message and entering in a code. At that point I just close the window and forget about it. There are better forums out there that don't require such nonsense. I don't even know how they got my phone number in the first place - probably because I have an Android phone that uses the account.

    On the other hand, I will happily use 2FA with my work VPN and my bank. There's something worth securing there. Google just set the bar too low. You want to send me a text message to confirm a comment on a YouTube video? No thanks.

    People used to complain that they had to remember too many passwords to different services. So now, everyone logs into everything via Google or Facebook, which makes them 10x more vulnerable. So now we have to use 2FA to secure everything because it is such a treasure trove of data. We were better-off the old way.

  55. Phone number? SMS? Yubikey? by Anonymous Coward · · Score: 1

    Yubikey and Lastpass. Even secures my computer with the former. You can even store PGP keys if one wants to do that. For those with a mobile phone there's a NFC version as well.

  56. What about other services? by antdude · · Score: 1

    Like Apple's, etc.?

    --
    Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
  57. quelle surprise! by Anonymous Coward · · Score: 0

    TFA is just a pain in the ass to use, I'm surprised that the numbers seem to be even in the higher one-digit percentage.

  58. Indeed by OneHundredAndTen · · Score: 2

    For, who uses gmail for anything serious?

  59. Re:Two-factor As Implemented Won't Work For Some U by Anonymous Coward · · Score: 0

    Get two U2F devices and associate them both to the account. If one gets lost, remove it and get another one. No clock or battery.

    My wife and I both do this for our own accounts, if she loses her device I help her get back in and vice-versa.

  60. Reason? by TemporalBeing · · Score: 1

    Android Apps and Third-Party Auth Integrations that don't support 2FA...

    Really...I enabled 2FA across my google accounts and had to disable it b/c I had too many things that didn't support the 2FA protocols. I still use the app password for Gmail though; it's still partially enabled in that respect. But until Android Apps and third-party auth integrations are forced to support it it won't go anywhere. I'd love to do so, especially using a FIDO/YubiKey solution; though again Android fails there as too many Android devices don't support the hardware tokens via USB, even with the dongles to hook them up.

    --
    Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    1. Re:Reason? by Anonymous Coward · · Score: 0

      U2F works over NFC or Bluetooth in Android, through the Google Authenticator.

  61. Because relying on sms is stupid by Anonymous Coward · · Score: 0

    Thanks to SS7, two factor authentication is less secure than a decent password. All the attacker needs is your phone number.

  62. A few thoughts by Anonymous Coward · · Score: 0

    ... Gmail Users Enable Two-Factor Authentication ...

    Google helped create the FIDO U2F standard and use it themselves but don't encourage their subscribers to use it. Google authenticator and other phone-based 2FA is primarily a way to link a real name and address to an account. Not that it matters, most people access their Google account from their phone anyway.

    Google allows a second FIDO U2F device to be linked to an account, allowing an account to be shared (without password sharing), or to be accessed when the first device is lost/stolen.

    ... a password manager to protect their accounts ...

    How can they tell? One can use a password manager without using its random-password generator. A few words about password managers: It allows mobility, which can be lost or stolen, so back-ups are necessary (I have 4). That won't help someone at the point of loss, but it will be possible to resume normal life in short order. It creates a single point of failure, so good AV and anti-spyware practices are needed. Plus, of course, use a manager that provides real encryption on mobile devices. So many Android apps move the data file to a hidden directory, then rename it, and possibly ROT cipher the first few kilobytes: That is fake security.

  63. two hard where it's most needed by Anonymous Coward · · Score: 0

    The places I most need 2FA are places where I will not have my phone and do not want to carry around a pad of one-use codes. (i.e. south east asian holidays).
    If I use a second email address for the 2FA then it's exactly the same problem, except they can get hack two emails instead of one.

  64. THIS!!! by Anonymous Coward · · Score: 0

    I bought a U2F device to secure more of my online accounts. I use google docs, but not gmail or any of the other google stuff.

        Wanted to secure my github account as well, but they wouldn't allow U2F without a cell phone connection either. Actually bought a $5 device through the github offer.

    Can't ever get google to respond, but github customer service did. I explained my desire and they checked if a cell phone was mandatory. It was.

    Too bad. That U2F device has been a complete waste.

  65. Probably because... by Anonymous Coward · · Score: 0

    ... No one in their right mind uses google email for anything private life (including contacts) or employment. Get a protonmail account. Better to use gmail for light use and get hacked than to give Google your phone number. If something looks fishy, just make another account for your website sign ups and spam.

  66. A password manager seems like a single point. by Maxo-Texas · · Score: 1

    It's one point to attack/corrupt/infiltrate.

    So I'm leery of using a password manager.

    Instead I have really long algorithmic passwords.

    --
    She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.
  67. annoying by Tom · · Score: 1

    2FA is more secure, but annoying. Massively annoying if you log into several 2FA secured accounts over the day. I'm accepting it for online banking and similarily important business, but not for my throwaway gmail accounts.

    Clef was 2FA done right, and I have high hopes for SQRL, but it seems slow in coming out with actual clients that normal people can use.

    As long as the usability factor for 2FA is somewhere between annoying and hostile, it won't see more adoption.

    --
    Assorted stuff I do sometimes: Lemuria.org
  68. CORRECTION: It was indeed out of date by tepples · · Score: 1

    I just checked, and the text is indeed out of date. I was able to set up 2FA for my account by using a Samsung Galaxy Tab A 8" (an Android tablet with Google Play) as my second factor instead of a cell phone.

    Twitter has some catching up to do.

    1. Re:CORRECTION: It was indeed out of date by AmiMoJo · · Score: 1

      Twitter's insistence on SMS is a real pain. In some countries I don't even have SMS reception capability, it's data only.

      These days all SMS and voicemail I get is spam anyway. I'd disable them if I could but my provider doesn't even allow it.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
  69. hacking by Anonymous Coward · · Score: 0

    This man assisted me in hacking my CHEATING HUSBAND Facebook account and he is a very good hacker for services like :whats-app, call logs, test messages etc. He delivers in 2hrs or less you can email him on ENRIQUEHACKDEMON11@GMAIL.COM or WhatsApp: +1(628)203-7005 ,he might ask for who referred you to him say Maddie

  70. Forced 2FA by Anonymous Coward · · Score: 0

    It is even worse than that
    If you travel or use a VPN, google forces you to use 2FA
    You must have your phone with you to log into your google account.

    So, if I am overseas and I lose my phone, I can't log into my account and disable it asap.
    there is a nice little button that says I don't have a phone - it does nothing except tell you to use the phone or your home computer.
    Yep, fly 14,000 kilometres to turn your stolen phone off - F*k'n hopeless

    I am very happy with my level of security, no one knows my password.
    If I have to log in from a computer I don't trust, I change the password as soon as I can.
    It's not that hard.

    Google - stuffing up things to work very well

  71. " virtually no one is using it" by Anonymous Coward · · Score: 0

    10% of the millions using Gmail is a long way from "no one"

  72. "Fewer" not "Less" by Anonymous Coward · · Score: 0

    Fewer than 1 in 10.

    You illiterate American cretins...

  73. Two factor vs cost and convenience by MoarSauce123 · · Score: 1

    Two factor authentication often means getting a text message and that requires typically a cell phone that comes with more or less significant cost. Sure, I have one, almost everyone has one, but I rarely use it and pulling it out just to fish for a one time key so that I can download my spam emails is highly inconvenient. It also defies any attempt in automation. I have my emails downloaded from the server every two hours. The volume is so large that I otherwise would clog up the various email accounts I deal with. I'd go for two factor if the second factor is a hardware dongle that authorizes a system to download emails. And yes, I do not use the slow, ad laden and clunky web portals of email providers. There you have it, other users may have different reasons.

  74. Why I don't two-factor authenticate Gmail by jrjarrett · · Score: 1

    I don't bother because my Gmail account is my throw-away account. It's the email I give out if I absolutely HAVE to, to sign up for some web site or something. I also know I have a fairly ("asdfasdf") password on it because I DON'T CARE. Things I do care about are under a different email, with strong passwords and TFA .

  75. The real issue by Anonymous Coward · · Score: 0

    It is more important to teach someone what not to click on then how to use a password manager. 2-factor authentication is important though and in my opinion should be forcibly enabled by websites that support it.

  76. fido u2f has low adoption, but is convenient. by bytestorm · · Score: 2

    I started using 2FA recently, before that unique passwords & pw manager. I've never been bitten by security problems, but I'm relatively low profile.

    Working with u2f (yubikey) and totp (google authenticator) has been a bit annoying. Most sites don't support u2f, or even 2FA in general. The ones I want to have 2FA, like my bank, do not or they implement it through sms/email. Some sites, like Facebook, have issues with multiple u2f tokens (ie. second and subsequent tokens do not work). It requires extra effort to get gmail working in external clients with saved device trust instead of 2FA as well.

    Actually using u2f has been nice though, even with chrome on android via nfc. Once things are set up on a site, it's very reliable.

  77. Who uses? by MercTech · · Score: 2

    Who uses a web based email server and expects security? Even back in the 90s people knew better than rely on Hotmail, Yahoo, and Gmail. I don't bother with high security on gmail as it is my throw away spamertizer catcher address used to sign onto web pages that require a valid email to read their articles.

    --
    NRRPT/RCT