This is a Go library that allows you to access your Authy TOTP tokens.
It was created to facilitate exports of your TOTP database, because Authy do not provide any way to access or port your TOTP tokens to another client.
It also somewhat documents Authy's protocol/encryption, since public materials on that are somewhat scarce.
Please be careful. You can get your Authy account suspended very easily by using this package. It does not hide itself or mimic the official clients.
This program will enrol itself as an additional device on your Authy account and export all of your TOTP tokens in Key URI Format.
Pre-built binaries are available from the releases page. (Windows binaries have been removed because of continual false positive virus complaints, sorry).
Alternatively, it can be compiled from source, which requires Go 1.12 or newer:
go install github.com/alexzorin/authy/cmd/authy-export@latest
To use it:
- The program will prompt you for your phone number country code (e.g. 1 for United States) and your phone number. This is the number that you used to register your Authy account originally.
- If the program identifies an existing Authy account, it will send a device registration request using the
pushmethod. This will send a push notification to your existing Authy apps (be it on Android, iOS, Desktop or Chrome), and you will need to respond that from your other app(s).
- If the device registration is successful, the program will save its authentication credential (a random value) to
$HOME/authy-go.jsonfor further uses. Make sure to delete this file and de-register the device after you're finished.
- If the program is able to fetch your TOTP encrypted database, it will prompt you for your Authy backup password. This is required to decrypt the TOTP secrets for the next step.
- The program will dump all of your TOTP tokens in URI format, which you can use to import to other applications.
If you notice any missing TOTP tokens, please try toggling "Authenticator Backups" in your Authy settings, to force your backup to be resynchronized.
How do you then import it into another app?
Up to you, depends on the app. If the app uses QR scanning, you can try stick all the dumped URIs into a file (
tokens) and then scan each QR code from your terminal, e.g.:
#!/usr/bin/env bash cat tokens | while IFS= read -r line; do clear echo -n "$line" | qrencode -t UTF8 read -p $"Press any key to continue" key < /dev/tty done
"My Twitch (or other site) token is different to the one I see in the Authy app?"
This is expected, depending on what the site is.
In Authy, there are two types of secrets:
- Tokens: You sign up to a website, the website generates a TOTP secret, and you scan it via a QR code (in any app, not necessarily Authy). You can export that secret to other TOTP apps and the code will match.
- Apps: The website has exported their TOTP flow to Authy's proprietary service, which requires you to use the Authy app. For sites like Twitch, Authy assigns a unique TOTP secret for every device you use the Authy app on. Each device will produce different 7-digit codes, but they will all work. If you deregister any device from your Authy account, that device's TOTP secrets will be revoked and its 7-digit codes will no longer work.
Twitch (and a handful of other sites) are the latter: Authy Apps.
authy-export registers itself as a device on your Authy account. Per the explanation above, that means it is assigned a unique TOTP secret for sites like Twitch, which means it will generate different 7-digit codes to your primary Authy device. These codes will work as long as you don't deregister the
authy-export device from your Authy account.
This is unfortunate, but the fact is: you cannot fully delete your Authy account if you want to keep using TOTP-based authentication with Twitch. If you do, all of the TOTP secrets will be revoked, and you will locked out of Twitch. It happened to me, and Twitch support chose to not help me out ^_^.
When environment variable named
authy-export does not ask for a password and uses the variable instead. Use with care!
Trademark Legal Notice
All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, logos, and brands does not imply endorsement