Jump to content

Google Authenticator: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
mNo edit summary
m →‎top: markup. wrapped programming languages in a {{plainlist}}
Line 18: Line 18:
| latest preview version =
| latest preview version =
| latest preview date = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->
| latest preview date = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->
| programming language = * [[Java (programming language)|Java]] (Android, Blackberry)
| programming language =
* [[Java (programming language)|Java]] (Android, Blackberry)
* [[Objective-C]] (iOS)
* [[Objective-C]] (iOS)
}}
| repo = {{URL|1=https://github.com/google/google-authenticator }}
| repo = {{URL|1=https://github.com/google/google-authenticator }}
| operating system = [[Android (operating system)|Android]], [[iOS]], [[BlackBerry OS]]
| operating system = [[Android (operating system)|Android]], [[iOS]], [[BlackBerry OS]]

Revision as of 08:11, 24 January 2021

Google Authenticator
Developer(s)Google
Initial releaseSeptember 20, 2010; 13 years ago (2010-09-20)[1]
Repositorygithub.com/google/google-authenticator
Written in
Operating systemAndroid, iOS, BlackBerry OS
PlatformMobile
LicenseProprietary freeware (earlier versions were under Apache License 2.0)

Google Authenticator is a software-based authenticator by Google that implements two-step verification services using the Time-based One-time Password Algorithm (TOTP; specified in RFC 6238) and HMAC-based One-time Password algorithm (HOTP; specified in RFC 4226), for authenticating users of software applications.[2]

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, Authenticator generates a six- to eight-digit one-time password which users must enter in addition to their usual login details.

Previous versions of the software were open-source but since 2013 releases are proprietary.[3]

Typical use case

To use Authenticator, the app is first installed on a smartphone. 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 username and password to the site, which computes (but does not display) the required six-digit one-time password and asks the user to enter it. 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, mere knowledge of username and password is not sufficient to break into a user's account; the attacker also needs knowledge of the shared secret key, or physical access to the device running the Authenticator app. An alternative route of attack is a man-in-the-middle attack: if the computer used for the login process is compromised by a trojan, then username, password and one-time password can be captured by the trojan, which can then initiate its own login session to the site or monitor and modify the communication between user and site.[citation needed]

Technical description

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).[4] This is transferred to the Authenticator app as a 16, 26 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 that is HMAC-ed can be:

  • the number of 30-second periods since the Unix epoch (TOTP); 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-digit code.

Pitfalls

Google Authenticator uses default parameters which are weaker than the suggestions in RFC 6238. Such defaults can be reasonably exploited, as demonstrated in Hashcat's TOTP cracking engine.[5] For this reason, operators using Google Authenticator should take care with the secrets being used.

Other authentication software

The Google Authenticator app for Android was originally open source, but later became proprietary.[3] Google made earlier source for their Authenticator app available on its GitHub repository; the associated development page states:

"This open source project allows you to download the code that powered version 2.21 of the application. Subsequent versions contain Google-specific workflows that are not part of the project."[6]

Following Google Authenticator ceasing to be open source, a free-software clone named FreeOTP[7][3] was created, predominantly a fresh rewrite but including some code from the original.

Google provides Android,[8] BlackBerry, and iOS[9] versions of Authenticator.

Several other versions of authentication software are available. Those that use TOTP and HMAC in addition to other two-factor authentication can authenticate with the same sites and processes as Google Authenticator. Some of the listed software is available in versions for several platforms.

  • Windows Phone 7.5/8/8.1/10: Microsoft Authenticator,[10] Virtual TokenFactor[11]
  • Windows Mobile: Google Authenticator for Windows Mobile[12]
  • Java CLI: Authenticator.jar[13]
  • Java GUI: JAuth,[14] FXAuth[15]
  • J2ME: gauthj2me,[16] lwuitgauthj2me,[17] Mobile-OTP (Chinese only),[18] totp-me[19]
  • Palm OS: gauthj2me[20]
  • Python: onetimepass[21] pyotp[22]
  • PHP: GoogleAuthenticator.php[23]
  • Ruby: rotp,[24] twofu[25]
  • Rails: active_model_otp[26]
  • webOS: GAuth[27]
  • Windows: gauth4win,[28] MOS Authenticator,[29] WinAuth[30]
  • .NET: TwoStepsAuthenticator[31]
  • Multi-platform: SAASPASS Authenticator
  • HTML5: html5-google-authenticator[32]
  • MeeGo/Harmattan (Nokia N9): GAuth[33]
  • Sailfish OS: SGAuth,[34] SailOTP[35]
  • Apache: Google Authenticator Apache Module[36]
  • PAM: Google Pluggable Authentication Module,[6] oauth-pam[37]
  • Backend: LinOTP (Management Backend implemented in python)
  • Browser extension: Authenticator[38]
  • Multi-platform: Authy[39][40]
  • Multi-platform: Duo Mobile[41]
  • Android, Apple iOS, and iPadOS: IBM Verify[42]
  • Apple iOS and iPadOS (with z/OS): IBM TouchToken[43]
  • OTP Auth[44]

See also

References

  1. ^ "Google Is Making Your Account Vastly More Secure With Two-Step Authentication - TechCrunch". TechCrunch. 2010-09-20. Retrieved 2016-03-12.
  2. ^ "GitHub - google/google-authenticator: Open source version of Google Authenticator (except the Android app)". GitHub. 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.
  3. ^ a b c Willis, Nathan (22 January 2014)."FreeOTP multi-factor authentication". LWN.net. Retrieved 10 August 2015.
  4. ^ "RFC 4226 - HOTP: An HMAC-Based One-Time Password Algorithm". Tools.ietf.org. 2005-02-15. Retrieved 2019-03-25.
  5. ^ "Attacking Google Authenticator". unix-ninja.
  6. ^ a b "google-authenticator - Two-step verification - Google Project Hosting".
  7. ^ "FreeOTP".
  8. ^ https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2 A
  9. ^ "Google Authenticator". App Store.
  10. ^ "Authenticator". 4 April 2013.
  11. ^ "Virtual TokenFactor". 26 February 2012.
  12. ^ "[APP]Google Authenticator for Windows Mobile". XDA Developers.
  13. ^ "http://blog dot jamesdotcuff dot net". Archived from the original on 2014-08-01. Retrieved 2012-01-19.
  14. ^ "mclamp/JAuth". GitHub.
  15. ^ "kamenitxan/FXAuth". GitHub.
  16. ^ "gauthj2me - Google Authentification in Java Mobile, j2me - Google Project Hosting".
  17. ^ "lwuitgauthj2me - Google Authenticator for J2ME phones - Google Project Hosting".
  18. ^ "chunlinyao / mobile-otp — Bitbucket".
  19. ^ "totp-me - TOTP for Java ME - Google authenticator".
  20. ^ "gauth.prc - gauthj2me - Google Authenticator for Palm OS (converted from java) - Google Authentification in Java Mobile, j2me - Google Project Hosting".
  21. ^ "tadeck/onetimepass". GitHub.
  22. ^ "pyotp/pyotp". GitHub.
  23. ^ "chregu/GoogleAuthenticator.php". GitHub.
  24. ^ "rotp - RubyGems.org - your community gem host".
  25. ^ "ukazap/twofu". GitHub.
  26. ^ "heapsource/active_model_otp". GitHub.
  27. ^ "GAuth".
  28. ^ "gauth4win - Google Authenticator for windows - Google Project Hosting".
  29. ^ "MOS Authenticator Home".
  30. ^ "winauth - Windows Authenticator for Battle.net / World of Warcraft / Guild Wars 2 / Glyph / WildStar / Google / Bitcoin - Google Project Hosting".
  31. ^ "glacasa/TwoStepsAuthenticator". GitHub.
  32. ^ "gbraad/html5-google-authenticator". GitHub.
  33. ^ Techtransit. "Nokia Store: Download GAuth and many other games, wallpaper, ringtones and mobile apps on your Nokia phone".
  34. ^ "SGAuth".
  35. ^ "SailOTP".
  36. ^ "google-authenticator-apache-module - Apache Module for Two-Factor Authentication via Google Authenticator - Google Project Hosting".
  37. ^ "oauth-pam - PAM for use with OAuth Websites - Google Project Hosting".
  38. ^ "Authenticator-Extension/Authenticator". GitHub.
  39. ^ Twilio Authy
  40. ^ "Authy". App Store.
  41. ^ "Duo Mobile". App Store.
  42. ^ "IBM Verify User Guide".
  43. ^ "IBM TouchToken". App Store.
  44. ^ "OTP Auth". App Store.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Google_Authenticator&oldid=1002406169"