We will be using ADB (Android Debug Bridge) to pull the database from the phone to your computer. So, root your phone that has the authenticator app installed. To access the SQLite database, we need root permission. Any Linux distro (tested on ubuntu 14.04).Should work everywhere as long as you have all dependencies installed (see below): You may experience 10 seconds offset between two devices. Keep in mind that you won't be able to have perfect match between two different devices. Try to play with "offset compensation" feature in authenticator settings if codes don't match Please check that both old and new devices have the same timezone and time The only thing that can fail here is time synchronisation between your different devices and different authenticator app vendors. Google authenticator exact version (you can check it in settings > about).
If it breaks for you, please open an issue with following information: So if the schema changes in new versions this method could break until i update the repository. Scripts in this repository highly depend on sqlite database schema of the authenticator app. Lastpass Authenticator v1.2 on Android 7.1 (rooted).Google Authenticator v2.49 on Android 4.2.1 (rooted).Removing and adding the 2FA from your online account (whatever it may) Works for me (TM) The idea is to extract the key and generate the QR code again so that you can scan it on a new app without having to worry about The authenticator apps (Google and Lastpass) stores this key on an SQLite3 database. Because of that, the key has to be stored somewhere in the device itself, Inorder for theĪpp to generate the OTP, it needs the shared key. To setup the MFA using the authenticator app(on any service), you are reading the shared key from the QR code. The TOTP (Time-based One-Time Password) is an OTP generated using a shared key and the current time.
0 kommentar(er)
