Jump to content

Google Authenticator

From Wikipedia, the free encyclopedia
Google Authenticator
DeveloperGoogle
ReleaseSeptember 20, 2010; 16 years ago (2010-09-20)[1]
Stable release(s) [±]
Android7.2 / June 26, 2026; 4 months ago (2026-06-26)[2][3]
iOS5.2 / November 4, 2026; 16 days ago (2026-11-04)[4]
Written in
Operating systemAndroid 9+,[a] iOS 17+[b]
Discontinued
LicenseProprietary freeware (some versions were under Apache License 2.0)
Repositorygithub.com/google/google-authenticator

Google Authenticator is a software-based authenticator by Google. It implements multi-factor authentication services using the time-based one-time password (TOTP; specified in RFC 6238) and HMAC-based one-time password (HOTP; specified in RFC 4226), for authenticating users of software applications.[5]

When logging into a site supporting Authenticator (including Google services) or using Authenticator-supporting third-party applications such as password managers or file hosting services,[citation needed] Authenticator generates a six-digit one-time password which users must enter in addition to their usual login details.[6]

Google provides Android,[7] BlackBerry, and iOS[8] versions of Authenticator. Authenticator started backing-up to the cloud in 2023 for logged-in users making it easier to switch devices.[9][10][6] It does not make it easy to switch between competitor products and collects more data than some of its competitors like Aegis or Stratum.[11] The app is relatively easy-to-use[10] and was the most prominent app for multi-factor authentication as of 2023.[12]

An official open source fork of the Android app is available on GitHub.[13] However, this fork was archived in April 6, 2021 and is now read only.[14] Current software releases are proprietary software.[15] Google does not end-to-end encrypt backups.[10]

Typical use case

[edit]
Previous logo
Screenshot of the Google Authenticator in April 2012, this was the open-source version

The app is first installed on a smartphone to use Authenticator.[6] It must be set up for each site with which it is to be used: the site provides a shared secret key to the user over a secure channel, to be stored in the Authenticator app. This secret key will be used for all future logins to the site.[citation needed]

To log into a site or service that uses two-factor authentication and supports Authenticator, the user provides a username and password to the site. The site then computes (but does not display) the required six-digit one-time password and asks the user to enter it.[6] The user runs the Authenticator app, which independently computes and displays the same password, which the user types in, authenticating their identity.[citation needed]

With this kind of two-factor authentication, knowledge of username and password is insufficient to get into a user's account - the attacker would need knowledge of the shared secret key or physical access to the device running the Authenticator app. A man-in-the-middle attack is another risk for users if their device used for the login process is compromised by malware, the credentials and one-time password can be intercepted by the malware, which then can initiate its login session to the site, or monitor and modify the communication between the user and the site.[16]

Technical description

[edit]

During setup, the service provider generates an 80-bit secret key for each user (whereas RFC 4226 §4 requires 128 bits and recommends 160 bits).[17] This is transferred to the Authenticator app as a 16, 24, or 32-character base32 string, or as a QR code.

Subsequently, when the user opens the Authenticator app, it calculates an HMAC-SHA1 hash value using this secret key. The message can be:

  • The number of 30-second periods since the Unix epoch (TOTP) as 64-bit big endian integer; or
  • A counter that is incremented with each new code (HOTP).

A portion of the HMAC is extracted and displayed to the user as a six- to eight-digit code; The last nibble (4 bits) of the result is used as a pointer, to a 32-bit integer, in the result byte array, and masks out the 31st bit.[citation needed]

License

[edit]

The Google Authenticator app for Android was open source upon launch in 2010 before becoming proprietary in 2013.[15] Google made earlier source code for their Authenticator app available on its GitHub repository where the latest open-source release was in 2020.[13][18]

See also

[edit]

Notes

[edit]
  1. ↑ Including Wear OS
  2. ↑ Including iPadOS

References

[edit]
  1. ↑ "Google Is Making Your Account Vastly More Secure With Two-Step Authentication". TechCrunch. 2010-09-20. Retrieved 2016-03-12.
  2. ↑ "Google Authenticator". Google Play. Retrieved November 11, 2026.
  3. ↑ "Google Authenticator 7.2". APKMirror. June 26, 2026. Retrieved November 11, 2026.
  4. ↑ "Google Authenticator". App Store. Retrieved November 11, 2026.
  5. ↑ "GitHub - google/google-authenticator: Open source version of Google Authenticator (except the Android app)". GitHub. 18 May 2022. These implementations support the HMAC-Based One-time Password (HOTP) algorithm specified in RFC 4226 and the Time-based One-time Password (TOTP) algorithm specified in RFC 6238.
  6. 1 2 3 4 Rogers, Reece (2023-05-14). "How to Use Google Authenticator". Wired. ISSN 1059-1028. Retrieved 2026-11-18.
  7. ↑ "Google Authenticator - Apps on Google Play".
  8. ↑ "Google Authenticator". App Store. 3 December 2020.
  9. ↑ Peachey, Jack (2026-11-08). "How to set up Google Authenticator on a new phone". Engadget. Retrieved 2026-11-17.
  10. 1 2 3 Eddy, Max (2026-04-08). "You Might Be Missing This Crucial Step in Your Online Security". The New York Times. ISSN 0362-4331. Retrieved 2026-11-17.
  11. ↑ Key, Kim (2026-03-16). "Google Authenticator Review: Simple Security With Some Strings Attached". PCMAG. Retrieved 2026-11-18.
  12. ↑ Taylor, Josh (2023-02-21). "Twitter is ending free SMS two-factor authentication. So what can you use instead?". The Guardian. ISSN 0261-3077. Retrieved 2026-11-17.
  13. 1 2 "google/google-authenticator-android: Open source fork of the Google Authenticator Android app". GitHub. 16 May 2022.
  14. ↑ "google-authenticator/mobile at master · google/google-authenticator". GitHub.
  15. 1 2 Willis, Nathan (22 January 2014)."FreeOTP multi-factor authentication". LWN.net. Retrieved 10 August 2015.
  16. ↑ Umawing, Jovi (6 January 2022). "Intercepting 2FA: Over 1200 man-in-the-middle phishing toolkits detected". www.malwarebytes.com. Retrieved 27 April 2023.
  17. ↑ m'Raihi, D.; Bellare, M.; Hoornaert, F.; Naccache, D.; Ranen, O. (2005-02-15). "RFC 4226: HOTP: An HMAC-Based One-Time Password Algorithm". RFC Editor. doi:10.17487/RFC4226. Retrieved 2019-03-25.
  18. ↑ "Google Authenticator OpenSource". GitHub.
[edit]