Google Authenticator is an application that implements TOTP security tokens from RFC 6238 in mobile apps made by Google, sometimes branded "two-step authentication". Authenticator provides a six to eight digit one-time password users must provide in addition to their username and password to log into Google services or other sites. The Authenticator can also generate codes for third party applications, such as password managers or file hosting services. Previous versions of the software were open source.
Contents
-
Typical use case 1
-
Implementations 2
-
Technical description 3
-
Pseudocode for Time OTP 3.1
-
Pseudocode for Event/Counter OTP 3.2
-
Open Source status on Android 4
-
Usage 5
-
References 6
-
External links 7
Typical use case
Typically, users will install the Authenticator app on their smartphone. To log into a site or service that uses two-factor authentication, they provide user name and password to the site and run the Authenticator app which produces an additional six-digit one-time password. The user provides this to the site, the site checks it for correctness and authenticates the user.
For this to work, a set-up operation has to be performed ahead of time: 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.
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 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.
Implementations
Google provides Android,[1] BlackBerry and iOS,[2] versions of Authenticator. Several third party implementations are available.
-
Windows Phone 7.5/8: Authenticator Virtual TokenFactor
-
Windows Mobile: Google Authenticator for Windows Mobile
-
Java CLI: Authenticator.jar
-
Java GUI: JAuth
-
J2ME: gauthj2me lwuitgauthj2me Mobile-OTP (chinese only) totp-me
-
Palm OS: gauthj2me
-
Python: onetimepass
-
PHP: GoogleAuthenticator.php
-
Ruby: gem (third party implementation)
-
Rails: active_model_otp (third party implementation)
-
webOS: GAuth
-
Windows: gauth4win MOS Authenticator WinAuth
-
.NET: TwoStepsAuthenticator
-
HTML5: html5-google-authenticator
-
MeeGo/Harmattan (Nokia N9): GAuth
-
Sailfish OS: SGAuth
-
Apache: Google Authenticator Apache Module
-
PAM: Google Pluggable Authentication Module oauth-pam
-
Backend: LinOTP (Management Backend implemented in python)
-
Chrome/Chrome OS: Authenticator
-
iOS: OTP Auth
Technical description
The service provider generates an 80-bit secret key for each user. This is provided as a 16, 24 or 32 character base32 string or as a QR code. The client creates an HMAC-SHA1 using this secret key. The message that is HMAC-ed can be:
-
the number of 30 second periods having elapsed since the Unix epoch; or
-
the counter that is incremented with each new code.
A portion of the HMAC is extracted and converted to a 6 digit code.
Pseudocode for Time OTP
function GoogleAuthenticatorCode(string secret)
key := base32decode(secret)
message := floor(current Unix time / 30)
hash := HMAC-SHA1(key, message)
offset := value of last nibble of hash
truncatedHash := hash[offset..offset+3] //4 bytes starting at the offset
Set the first bit of truncatedHash to zero //remove the most significant bit
code := truncatedHash mod 1000000
pad code with 0 until length of code is 6
return code
Pseudocode for Event/Counter OTP
function GoogleAuthenticatorCode(string secret)
key := base32decode(secret)
message := counter encoded on 8 bytes
hash := HMAC-SHA1(key, message)
offset := last nibble of hash
truncatedHash := hash[offset..offset+3] //4 bytes starting at the offset
Set the first bit of truncatedHash to zero //remove the most significant bit
code := truncatedHash mod 1000000
pad code with 0 until length of code is 6
return code
Open Source status on Android
The Authenticator app as available on Google's Android app market is proprietary, as explained on the project's development page:
"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."[3]
An independent fork of the Android version of the software named OTP Authenticator[4] has been created, which is based on the last version of the open source code that had been provided by Google. Another Open Source fork named FreeOTP[5] has been published by Red Hat.
Usage
Google Authenticator can be used for the following websites and applications:
References
-
^ Android version of Google Authenticator
-
^ iOS version of Google Authenticator
-
^ Open Source status of Google Authenticator on Android
-
^ OTP Authenticator, an Open Source fork of the Android app
-
^ https://fedorahosted.org/freeotp/
-
^ http://aws.amazon.com/
-
^ Added security for your App.net account
-
^ Update: Bitstamp adds support for two-factor authentication
-
^ https://blockchain.info/nl/wallet/google-authenticator
-
^ https://btc-e.com/
-
^ https://bufferapp.com/2step
-
^ https://cex.io/r/1/johs633new/0/ Cex.io bitcoin commodity exchange
-
^ CipherGraph adds Two-Factor Authentication to CipherGraph Cloud Access Gateway Cloud Security Solution
-
^ https://coinbase.com/security
-
^ https://www.cryptsy.com/pages/security
-
^ Dashlane Adds Two-Factor Authentication, a New Interface, and More (Lifehacker)
-
^ DigitalOcean Features
-
^ Enabling Multifactor Authentication
-
^ Dropbox with Google Authenticator
-
^ http://blog.evernote.com/blog/2013/05/30/evernote-talks-2-step-verification/
-
^ Use Facebook’s 2-factor Authentication with Third-Party TOTP Generators
-
^ https://wiki.gandi.net/en/contacts/login/2-factor-activation
-
^ https://github.com/blog/1614-two-factor-authentication
-
^ https://help.hover.com/entries/26677644-How-to-Enable-two-step-signin-on-your-Hover-account
-
^ http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemEdit&tracker_item_id=31704
-
^ https://www.kickstarter.com/help/faq/backer+questions?ref=faq_livesearch#faq_63004
-
^ LastPass with Google Authenticator
-
^ Linode Manager Two-Step Authentication
-
^ LinOTP LinOTP Management Backend
-
^ Login - Google Authenticator for Desktop (lightdm or gdm plugin) - Ask Ubuntu
-
^ Boost your account security thanks to Mt.Gox's new Security Center
-
^ Blog post about addition of TOTP authentication to Nearlyfreespeech
-
^ http://www.pobox.com/helpspot/index.php?pg=kb.printer.friendly&id=21#p363
-
^ http://services.runescape.com/m=news/a=13/runescape-authenticator?jptg=ia&jptv=community_news
-
^ https://trustedspace.agitos.de/webgui/
-
^ http://www.tumblr.com/docs/en/two_factor_auth
-
^ http://doxfer.webmin.com/Webmin/EnhancedAuthentication
-
^ http://wildstar-online.com
External links
-
Google Authenticator on Google Help
-
Google Authenticator open source project on Google Code
-
Google Authenticator implementation in Python on Stack Overflow
-
Google Authenticator Android package at the F-Droid repository
This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.