HMAC-based One-time Password Algorithm
HOTP is an HMAC-based One Time Password algorithm. It is a cornerstone of Initiative For Open Authentication (OATH).
HOTP was published as an informational IETF RFC 4226 in December 2005, documenting the algorithm along with a Java implementation. Since then, the algorithm has been adopted by many companies worldwide (see below). The HOTP algorithm is a freely available open standard.
Contents
- 1 Definition
- 2 Applications
- 3 Tokens
- 4 Reception
- 5 Implementations
Definition
Let:- K be a secret key
- C be a counter
- HMAC(K,C) = SHA1(K ⊕ 0x5c5c… ∥ SHA1(K ⊕ 0x3636… ∥ C)) be an HMAC calculated with the SHA-1 cryptographic hash algorithm
- Truncate be a function that selects 4 bytes from the result of the HMAC in a defined manner
- HOTP(K,C) = Truncate(HMAC(K,C)) & 0x7FFFFFFF
For HOTP to be useful for an individual to input to a system, the result must be converted into a HOTP value, a 6–8 digits number that is implementation dependent.
- HOTP-Value = HOTP(K,C) mod 10d, where d is the desired number of digits
Applications
HOTP can be used to authenticate a user in a system via an authentication server. Also, if some more steps are carried out (the server calculates subsequent OTP value and sends/displays it to the user who checks it against subsequent OTP value calculated by his token), the user can also authenticate the validation server.Tokens
Both hardware and software tokens are available from various vendors, for some of them see references below. Hardware tokens implementing OATH HOTP tend to be significantly cheaper than their competitors based on proprietary algorithms. As of 2010, OATH HOTP hardware tokens can be purchased for a marginal price.Some products can be used for strong passwords as well as OATH HOTP.Software tokens are available for (nearly) all major mobile/smartphone platforms (J2ME,Android, iPhone,BlackBerry,Maemo, Mac OS X, Windows Mobile).
Reception
Although the reception from some of the computer press has been negative during 2004 and 2005,after IETF adopted HOTP as RFC 4226 in December 2005, various vendors started to produce HOTP compatible tokens and/or whole authentication solutions (see above/below).According to a paper on strong authentication (entitled "Road Map: Replacing Passwords with OTP Authentication") published by Burton Group (a division of Gartner, Inc.) in 2010, "Gartner's expectation is that the hardware OTP form factor will continue to enjoy modest growth while smartphone OTPs will grow and become the default hardware platform over time."
Implementations
- Authy is an Android/iOS app for 2 factor authentication using TOTP.
- Barada Android app for the client side and PAM module for the server side.
- Duo Push is an HOTP based Android/iOS app for 2 factor authentication which utilizes Out-of-band Push technology for vastly increased security and ease of use.
- Google Authenticator open-source client for Android, iOS, and BlackBerry, and also PAM module for the server side.
- LinOTP is an opensource server implementation for HOTP and other tokens.
- multiOTP is an opensource PHP implementation for HOTP, TOTP, mOTP and other tokens. It can be used as a command line tool, integrated in a web site, as a web service, as a radius plugin, etc.
- OATH Toolkit GNU library and command line implementation of client for Linux systems, and also PAM module for the server side.
- OpenAM is an open source Java based Single Sign On server that supports various HOTP and TOTP client authenticators.
- privacyIDEA is an authentication backend that supports HOTP, TOTP, OCRA, mOTP and other token types like ssh public keys.
- SailOTP, a free software Sailfish OS client.
- YubiKey implements both HOTP as well as the OpenPGP card protocol. The hardware devices appear as USB keyboards and "type" the one-time password when their button is pressed.
