Command-line OTP calculator, with automatic password creation/storage.

Clone this repo:


  1. a435ced Add a feature to print out a URL for a QR code for the give TOTP by Greg Stein · 7 weeks ago master
  2. ecb14d8 Add support for TOTP. by Greg Stein · 7 weeks ago
  3. 7fad18c remove unused imports by Greg Stein · 5 months ago
  4. b865516 expand info on .otp by Greg Stein · 5 months ago
  5. 0e09dd2 Update by Greg Stein · 11 months ago

Command-line OTP calculator, with automatic password creation/storage.

Apache Specific

The Apache Software Foundation (ASF) uses the Orthrus PAM module on its machines/VMs. Orthrus implements RFC 2289 to offer One Time Password (OTP) challenges, in order to sudo. That package emits MD5-based challenges (otp-md5), so this script only constructs MD5-based responses.


The challenge presented by Orthrus can be copy/pasted onto the command line, or (absent command line args) into the Challenge? prompt.

[remote]$ sudo bash
otp-md5 440 someseed ext

[local]$ ./
Challenge? otp-md5 440 someseed ext
NOTE: copied to clipboard

or [local]$ ./ otp-md5 440 someseed ext

Note that you must copy/paste the challenge string from the remote host to the prompt on the local host. The response can then be pasted into the remote host's Password: prompt.

If the local host has the xclip or pbcopy program, then the reponse will be automatically copied to the clipboard. If that is not present, or does not exit with success, then the response string can be manually copied, then pasted to the remote.

The algorithm (“otp-md5”) is the default, and the only supported algorithm at the moment. On both the command line and the Challenge? prompt, that may be omitted. For example:

[local]$ ./
Challenge? 440 someseed ext
NOTE: copied to clipboard


[local]$ ./ 440 someseed ext
NOTE: copied to clipboard

Note that some Orthus implementations produce extra words (eg. ext). These will be ignored. The important parts are the algorithm (optional), the sequence, and the seed values.

The algorithm associated with a seed will be stored into the .otp file, and will override any future specification of an algorithm. Or, it shall provide the algorithm when it is not explicit on the command line or challenge prompt. In all cases, otp-md5 is the current default.

Alternative Usage

The script examines the program name used to invoke it (sys.argv[0]), and if that name matches a defined algorithm (otp-*), then it will use the command line arguments to select the sequence and seed.

For example:

[local]$ ln -s $somewhere/ otp-md5
[local]$ otp-md5 440 someseed ext
NOTE: copied to clipboard

Note that the challenge string from [remote] is directly pasted to the shell prompt.


$ ./ --test

This will run a few internal tests. Any problems will raise an AssertionError

Seeds and Passwords

If new seed is seen (ie. by running ortpasswd), then will construct a new password and store the seed and password into $HOME/.otp. The password will be used the next time the seed is seen.

Format of .otp

The .otp file is a list of single lines, containing the algorithm, the seed, and the password for that seed. For example:

otp-md5 someseed password-goes-here

Since spaces are not allowed in the algorithm or seed, these lines are easily parsed. Note that spaces are allowed in the password, so the password consists of the rest of the line.

Manually editing .otp

It is fine to append lines to .otp if you are carrying over seed/password values from another system (eg. SKeyCalc on older macOS machines). If you need to reset a password for a given seed, then remove the old line and go through the process to generate a new seed/password combination (and note that you'll also need to reset the Orthus state on the target machine).

Converting from SKeyCalc

The SKeyCalc application on macOS was a great tool for RFC 2289 challenges; however, it has not been updated for the latest macOS and is no longer usable. is a suitable replacement.

Instead of resetting your Orthus configuration on every machine, it is possible to copy the settings from SKeyCalc into your .otp file. This is a manual process using the Keychain Access application (it may be possible to use a keyboard macro utility to simplify this process).

  • Start Keychain Access
  • In the search box in the upper-right, enter skey; the listing should show all of your stored SKeyCalc passwords
  • For each password, double-click to open the Info (or use the Get Info menu item)
  • Select Show password
  • Copy the Account (which is the seed) and the password into a new line in your .otp file (remember to include otp-md5 at the beginning of each line).
  • Repeat

Possible TODO Items

  • Use the keyring python package to support keyrings instead of a plaintext file
  • Handle MD4 and SHA1 challenges
  • Track RFC 2289 more closely in “acceptable” inputs


Licensed under the Apache License, v2.0