Jump to content

Talk:Google Authenticator

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Rushyo (talk | contribs) at 12:52, 4 August 2015 (Added statement around RFC compliance). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

WikiProject iconGoogle Start‑class Low‑importance
WikiProject iconThis article is within the scope of WikiProject Google, a collaborative effort to improve the coverage of Google and related topics on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StartThis article has been rated as Start-class on Wikipedia's content assessment scale.
LowThis article has been rated as Low-importance on the project's importance scale.
WikiProject Google To-do:

Here are some tasks awaiting attention:
WikiProject iconSoftware: Computing Start‑class Low‑importance
WikiProject iconThis article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
StartThis article has been rated as Start-class on Wikipedia's content assessment scale.
LowThis article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing (assessed as Low-importance).

Can be used for ... ??

Facebook is in the list, I have turned on 2-step, but not with Google Authenticator, but with SMS to my mobile. I think it should be taken out, as I did not find any instruction on how to use GA. Edoderoo (talk) 21:23, 10 March 2013 (UTC)[reply]

It doesn't use the same Android Google Authenticator app, but it is compatible. I just tried it. I followed these steps:
Log into Facebook on a desktop computer, and go to your Settings menu, select Security on the left-hand sidebar. Edit the Login Approvals section. Click on "Using an Android or iPhone? Set up Code Generator", and click on the "Having trouble?" button. Click "Get key". On your device running Google Authenticator, prepare to set up a new account in the Authenticator. In Android, this is Menu > Set up account > Enter key provided. Enter the key provided after you press "Get key". Leave the option "Time-based". You'll then get an opportunity to test the key. edit: I also noticed that there's a set of instructions dated January 2013 in the citation next to the Facebook entry (at this time citation number 7) --BurritoBazooka (talk) 13:16, 12 May 2013 (UTC)[reply]
OK, then it was there for a good reason! Edoderoo (talk) 17:29, 12 May 2013 (UTC)[reply]

Usage

There is a trend toward more and more online companies enabling two-factor authentication (and especially Google Authenticator). This list could easily be hundreds of services long by the end of this year if it stays comprehensive. Wouldn't it be better to describe the types of services that support Google Authenticator and maybe list a few from each category? — Preceding unsigned comment added by Ramigem (talkcontribs) 22:37, 11 June 2013 (UTC)[reply]

Blacklisted Links Found on Google Authenticator

Cyberbot II has detected links on Google Authenticator which have been added to the blacklist, either globally or locally. Links tend to be blacklisted because they have a history of being spammed or are highly inappropriate for Wikipedia. The addition will be logged at one of these locations: local or global If you believe the specific link should be exempt from the blacklist, you may request that it is white-listed. Alternatively, you may request that the link is removed from or altered on the blacklist locally or globally. When requesting whitelisting, be sure to supply the link to be whitelisted and wrap the link in nowiki tags. Please do not remove the tag until the issue is resolved. You may set the invisible parameter to "true" whilst requests to white-list are being processed. Should you require any help with this process, please ask at the help desk.

Below is a list of links that were found on the main page:

  • https://cex.io/r/1/johs633new/0/
    Triggered by \bcex\.io\b on the global blacklist

If you would like me to provide more information on the talk page, contact User:Cyberpower678 and ask him to program me with more info.

From your friendly hard working bot.—cyberbot IITalk to my owner:Online 03:48, 14 May 2015 (UTC)[reply]

RFC compliance

The article claims Google Authenticator implements RFC 6238, however this is untrue and isn't properly cited. The software implements something similar to RFC 6238, however patently isn't compliant with RFC 4226's requirements (required by RFC 6238) due to using an 80-bit shared secret, as detailed here: https://security.stackexchange.com/questions/45053/why-does-google-cripple-the-2fa-google-authenticator-pam-module and can been observed at https://github.com/google/google-authenticator/blob/f0d1574734b5855d4a604d58be25fc1159563b66/libpam/google-authenticator.c. According to my own discussions with Google a few years ago when I noticed this myself, this is 'by design'. I'd suggest, unless we can provide a positive non-first party citation for it being compliant with RFC 6238 (true or otherwise), we either remove all reference to it or point out it only claims compliance, rather than actually being compliant. -Rushyo Talk 12:52, 4 August 2015 (UTC)[reply]