RSA SecurID-compatible software token for Android
Java
Switch branches/tags
Latest commit b844ec6 Dec 20, 2014 @cernekee cernekee Update changelog and bump version to v0.91-final (919)
Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Permalink
Failed to load latest commit information.
.settings
external
libs
res
screenshots
src
.classpath
.gitignore
.gitmodules
.project
.travis.yml
AndroidManifest.xml
CHANGES
COPYING
README.md
build.xml
ic_launcher-web.png
proguard-project.txt
project.properties

README.md

Easy Token

Easy Token is an RSA SecurID-compatible software authenticator for Android with advanced usability features:

  • Convenient lock screen and home screen widgets provide instant tokencodes without navigating to an app.
  • Optionally save your PIN.
  • Supports SDTID files, importing http://127.0.0.1/... tokens from email, and QR tokens.
  • 100% open source: https://github.com/cernekee/EasyToken

Downloads

Official releases are posted in the XDA thread and on Google Play.

No registration is required to download from XDA.

Support

To report issues, please email the author at cernekee@gmail.com or post in the XDA thread.

Screenshots

screenshot-0  screenshot-1

screenshot-2  screenshot-3

Building from source

On the host side you'll need to install:

  • NDK r10d, nominally under /opt/android-ndk-r10d
  • Host-side gcc, make, etc. (Red Hat "Development Tools" group or Debian build-essential)
  • git, autoconf, automake, and libtool
  • Android SDK in your $PATH (both platform-tools/ and tools/ directories)
  • javac 1.6 and a recent version of Apache ant
  • Use the Android SDK Manager to install API 19

First, clone the source trees:

git clone git://github.com/cernekee/EasyToken
cd EasyToken
git submodule update --init

Then build the binary components (libs/ directory):

make -C external NDK=/opt/android-ndk-r10d

Then build the Java components:

android update project -p .
ant debug

Build logs can be found on this project's Travis CI page.

Security considerations

Please use Easy Token responsibly and avoid taking unnecessary risks with sensitive data. All software tokens are at risk of theft by malware; for high-security applications a hardware token is strongly preferred.

Saving your PIN is convenient, but can be risky if your device is stolen.

If you use the lock screen widget, your tokencode is available to anybody with access to your phone (even if they cannot unlock it). For this case, you may want to ask your system administrator to issue a 6-digit PIN-less software token, which will require you to enter PIN + TOKENCODE when logging in, instead of just a tokencode.