Tools for programmable tokens

Burner apps and config tools for TOTP tokens


Special Android, iPhone, or Windows applications (i.e. Token2 Burner app) should be used to "burn" the secret hash seeds. The apps require an NFC module to operate. Cross-platform (Python) solution is also available for some models (and coming soon for others). This table below provides a list of the available burner applications or configuration tools for different models of Token2 programmable tokens. The table is interactive: you can choose the token model in the first column, then the platform in the second column to see if the combination is supported.



Choose a token model  Choose platform 
miniOTP-1, C105 Android Google Play
miniOTP-1, C105 Windows Burner.exe command line tool
C301, C302 Android Token2 NFC Burner2
C301, C302 cross-platform (Python) token2_config.py
C301-i, C302-i Android Token2 NFC Burner2
C301-i, C302-i Windows Windows NFC Burner (GUI)
Command-line tool
C301-i, C302-i iPhone iPhone app guide
C301-i, C302-i cross-platform (Python) token2_config.py
miniOTP-2, miniOTP-3 Android Token2 NFC Burner2
miniOTP-2, miniOTP-3 Windows Windows NFC Burner (GUI)
Command-line tool
OTPC-P1, OTPC-P2 Android Token2 NFC Burner2
OTPC-P1, OTPC-P2 Windows Windows NFC Burner (GUI)
Command-line tool
miniOTP-2-i, miniOTP-3-i Android Token2 NFC Burner2
miniOTP-2-i, miniOTP-3-i Windows Windows NFC Burner (GUI)
Command-line tool
miniOTP-2-i, miniOTP-3-i iPhone iPhone app guide
OTPC-P1-i, OTPC-P2-i Android Token2 NFC Burner2
OTPC-P1-i, OTPC-P2-i Windows Windows NFC Burner (GUI)
Command-line tool
OTPC-P1-i, OTPC-P2-i iPhone iPhone app guide
miniOTP-2-i, miniOTP-3-i cross-platform (Python) token2_config.py
OTPC-P1-i, OTPC-P2-i cross-platform (Python) token2_config.py
Molto-1 Android Android app guide
Molto-1 Windows Windows app guide
Molto-1-i  Android Android app guide
Molto-1-i  Windows Windows app guide
Molto-1-i  iPhone iPhone app guide
Molto-1-i  cross-platform (Python) molto1_config.py
EVVIS-QR-1  Windows EVVIS-QR1 USB Config tool
Molto-2  Windows Molto-2 USB Config tool
Molto-2v2 Windows Molto-2 USB Config tool
Command-line tool
Molto-2v2  cross-platform (Python) molto2.py
Default access keys
Important! Please make sure you use the correct application, as using a wrong app may lock the device out.  While this authentication is implemented in some models (Molto1 and Molto2 etc.), in some models, such as C301, OTPC* and miniOTP* cards, NFC access is left unrestricted by design.    We use ready components for our cards (often called Java-chips) and they have by default NFC access authentication, the access key was hard coded , currently  "8A D20 688 3CA3 694 82 AB2 7182 B6E 832 24" for single profile tokens (which cannot be changed) and "544 F4B 454 E32 4D4 F4C 544 F31 2D4 B4 55 9" for multi-profile models (which can be changed) ; removing authentication routine completely would make the final cost of the products higher. While this does not compromise security (as it is only possible to write the seeds and never read) , using a wrong app will damage the card for this reason.


Prerequisites


NFC Tokens

Android devices should be equipped with an NFC chip. iPhone apps are compatible with models newer than iPhone 7 and with iOS v13 or higher.  Windows application will require an external USB NFC reader or a built-in NFC module (existing on some models of modern laptops). So far the application has only been tested under Windows 10 and Windows 8 64 bit. Python-based NFC Burner script (token2_config.py) requires the PN533-chip based NFC Writer device.


USB Tokens

No additional device, driver nor any other installation is needed. USB cable is supplied (USB-A to micro-USB port), any standard USB cable can be used (with data support). For computers without USB-A ports, USB-Type-C adapters can be used.


Some devices (including some models of Android phones, such as Nexus and Pixels, some versions of ACR122 USB module) may have issues with NFC link stability, so please be patient when performing these operations. Read this article explaining the NFC link stability issues