Repository navigation
Releases
v1.1.0 - both cores, QR import
Two Windows builds of Google Authenticator, one running Google's original
BlackBerry passcode code and one running their original Android passcode
code, so the two can be compared directly.
Install
Download and run GoogleAuthenticator-Setup.exe. It installs both editions for
your user only — no administrator rights. Or use
GoogleAuthenticator-portable.zip and run the exes straight from the folder.
Java is not required; a trimmed runtime is bundled.
Windows SmartScreen will warn you. These builds are not code-signed, so
you will see "Windows protected your PC". Click More info → Run anyway.
Verify the download againstSHA256SUMS.txtbelow if you want to be sure.
What is in it
- Two editions sharing one UI and one bundled runtime:
GoogleAuthenticatorBlackBerry.exeandGoogleAuthenticatorAndroid.exe - QR import — load a saved screenshot or photo of a setup code
- Manual entry — type a secret, or paste an
otpauth://link - Encrypted storage — AES-256-GCM vault, PBKDF2-HMAC-SHA256, separate per
edition. There is no password recovery.
Verified
- RFC 4226 test vectors, counters 0-9: both editions match the published values
- 4,000 random secret/counter pairs: 0 differences between the editions
- QR encode/decode round trip at 200px and 512px
Run the checks yourself with windows/verify.ps1.
Known difference, left unfixed
The BlackBerry PasscodeGenerator accepts a passcode length but hardcodes
PIN_MODULO = 10^6; the Android one indexes DIGITS_POWER[codeLength] and is
correct. Both apps use 6 digits so they agree in practice. The bug is preserved
rather than patched — the point is to run the original code unchanged.
Checksums
c54d778748e2e14f10c458295f9b539724ea56eccbd461608a6c341ff19ecc9a GoogleAuthenticator-Setup.exe
b648b42808d4e205b2daa0bde4e02951ba7af9bbc13a8ce9e1813672a826aaa5 GoogleAuthenticator-portable.zip
Passcode generation is Google code under Apache 2.0, reused unmodified; see
NOTICE in the repository.