You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: FAQ.md
+11-2
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ When Flipper Authenticator is running `totp` CLI is available for you to list, a
34
34
35
35
**YES!**
36
36
37
-
Just pick the token you would like to auto-type then hold "arrow down" button for 1-2sec. and Flipper Authenticator will type it instead of you 😀
37
+
Just pick the token you would like to auto-type then hold <spantitle="Arrow Down">▼</span> button for 1-2sec. and let Flipper Authenticator type it instead of you 😀
38
38
39
39
## How to change\recover PIN?
40
40
@@ -49,6 +49,15 @@ To do that you may use following CLI commands:
49
49
50
50
All token secrets are stored in encrypted form and are tied to an original Flipper device and PIN. Given that, there is no sense to try to backup `/ext/apps/Misc/totp.conf` file as it will not help you in situation when you loose your Flipper device. Instead use your favorite password manager to store plain token secrets and\or any other information which will help you recover your accounts.
51
51
52
+
## How to reset application?
53
+
54
+
There are two options to reset Flipper Authenticator to its default:
55
+
56
+
1. Delete `/ext/authenticator/totp.conf` file
57
+
2. Use `totp reset` CLI command
58
+
59
+
**Regardless of which option you use, please pay attention to the fact that <ins>you will loose everything you configured and added to Flipper Authenticator application, including token secrets.</ins>**
There are multiple reasons why Flipper Authenticator generates invalid codes:
@@ -67,4 +76,4 @@ Sometimes it is possible that you just made a mistake while typing or copying to
67
76
68
77
### Token hashing algorithm is not correct
69
78
70
-
In majority of situation using default hashing algorithm `SHA1` should work just fine. But for some rare providers it might be necessary to use `SHA256` or `SHA512` as a hashinig alogorithm.
79
+
In majority of situations using default hashing algorithm `SHA1` should work just fine. But for some rare providers it might be necessary to use `SHA256` or `SHA512` as a hashinig alogorithm.
0 commit comments