|
|
3 лет назад | |
|---|---|---|
| .github | 3 лет назад | |
| flipperzero-firmware_official @ d1843c0094 | 3 лет назад | |
| flipperzero-firmware_unleashed @ 515e6db69c | 3 лет назад | |
| totp | 3 лет назад | |
| .gitattributes | 3 лет назад | |
| .gitignore | 3 лет назад | |
| .gitmodules | 3 лет назад | |
| LICENSE | 3 лет назад | |
| README.md | 3 лет назад | |
| build.ps1 | 3 лет назад | |
| fbt.ps1 | 3 лет назад |
Flipper Authenticator is a software-based authenticator that implements two-step verification services using the Time-based One-time Password (TOTP; specified in RFC 6238) and HMAC-based One-time Password algorithm. It is like Google Authenticator, but for Flipper Zero device.
If you don't want to build the app yourself then just pull FAP file from latest release and put it to your Flipper Zero device by copying it to /ext/apps/Misc. After that you should be able to run it on your Flipper.
Pull the repo with recursive submodule initialization and then run ./build.ps1 command to build the app. Once done FAP files will be available in the build directory.
At first start app will create new config file (default location is /ext/apps/Misc/totp.conf).
Detailed description of file format can be found here
Flipper Authenticator stores token secrets in config file in encrypted form. Encryption is done using standard Flipper Zero API, which states that it is using AES encryption with built-in into flipper secret key and initialization vector (IV) generated by the app at initial setup XOR-ed by user's PIN.
So in theory to get plain token secret it is necessary to have original Flipper Zero device where config file was generated and know user's PIN.
If user provides plain token secret manually straight to a config file, once app will be launched it will detect plain token, will encrypt it and will replace plain token secret with encrypted copy.
Let me know if you have an ideas of how we can make Flipper Authenticator even more secure.