|
@@ -10,7 +10,7 @@ A guide written by Green, an ente.io lover
|
|
> [!WARNING]
|
|
> [!WARNING]
|
|
>
|
|
>
|
|
> Authy will soon be dropping support for its desktop apps in the near future.
|
|
> Authy will soon be dropping support for its desktop apps in the near future.
|
|
-> If you are looking to switch to ente Authenticator from Authy, I heavily
|
|
|
|
|
|
+> If you are looking to switch to Ente Authenticator from Authy, I heavily
|
|
> recommend you export your codes as soon as you can.
|
|
> recommend you export your codes as soon as you can.
|
|
|
|
|
|
---
|
|
---
|
|
@@ -19,7 +19,7 @@ Migrating from Authy can be tiring, as you cannot export your 2FA codes through
|
|
the app, meaning that you would have to reconfigure 2FA for all of your accounts
|
|
the app, meaning that you would have to reconfigure 2FA for all of your accounts
|
|
for your new 2FA authenticator. However, easier ways exist to export your codes
|
|
for your new 2FA authenticator. However, easier ways exist to export your codes
|
|
out of Authy. This guide will cover two of the most used methods for mograting
|
|
out of Authy. This guide will cover two of the most used methods for mograting
|
|
-from Authy to ente Authenticator.
|
|
|
|
|
|
+from Authy to Ente Authenticator.
|
|
|
|
|
|
> [!CAUTION]
|
|
> [!CAUTION]
|
|
>
|
|
>
|
|
@@ -39,7 +39,7 @@ hard (and rather technical) parts of the process.<br><br>
|
|
|
|
|
|
One way to export is to
|
|
One way to export is to
|
|
[use this tool by Neeraj](https://github.com/ua741/authy-export/releases/tag/v0.0.4)
|
|
[use this tool by Neeraj](https://github.com/ua741/authy-export/releases/tag/v0.0.4)
|
|
-to simplify the process and skip directly to importing to ente Authenticator.
|
|
|
|
|
|
+to simplify the process and skip directly to importing to Ente Authenticator.
|
|
|
|
|
|
To export from Authy, download the tool for your specific OS, then type the
|
|
To export from Authy, download the tool for your specific OS, then type the
|
|
following in your terminal:
|
|
following in your terminal:
|
|
@@ -72,7 +72,7 @@ For Windows:
|
|
```
|
|
```
|
|
|
|
|
|
This will generate a text file called `authy_codes.txt`, which contains your
|
|
This will generate a text file called `authy_codes.txt`, which contains your
|
|
-Authy codes in ente's plaintext export format. You can now import this to ente
|
|
|
|
|
|
+Authy codes in Ente's plaintext export format. You can now import this to Ente
|
|
Authenticator!
|
|
Authenticator!
|
|
|
|
|
|
## Method 2: Use gboudreau's GitHub guide
|
|
## Method 2: Use gboudreau's GitHub guide
|
|
@@ -89,23 +89,23 @@ To export your data, please follow
|
|
|
|
|
|
This will create a JSON file called `authy-to-bitwarden-export.json`, which
|
|
This will create a JSON file called `authy-to-bitwarden-export.json`, which
|
|
contains your Authy codes in Bitwarden's export format. You can now import this
|
|
contains your Authy codes in Bitwarden's export format. You can now import this
|
|
-to ente Authenticator!
|
|
|
|
|
|
+to Ente Authenticator!
|
|
|
|
|
|
### Method 2.1: If the export worked, but the import didn't
|
|
### Method 2.1: If the export worked, but the import didn't
|
|
|
|
|
|
> [!NOTE]
|
|
> [!NOTE]
|
|
>
|
|
>
|
|
> This is intended only for users who successfully exported their codes using
|
|
> This is intended only for users who successfully exported their codes using
|
|
-> the guide in method 2, but could not import it to ente Authenticator for
|
|
|
|
|
|
+> the guide in method 2, but could not import it to Ente Authenticator for
|
|
> whatever reason. If the import was successful, or you haven't tried to import
|
|
> whatever reason. If the import was successful, or you haven't tried to import
|
|
> the codes yet, ignore this section.
|
|
> the codes yet, ignore this section.
|
|
>
|
|
>
|
|
> If the export itself failed, try using
|
|
> If the export itself failed, try using
|
|
> [**method 1**](#method-1-use-neerajs-export-tool) instead.
|
|
> [**method 1**](#method-1-use-neerajs-export-tool) instead.
|
|
|
|
|
|
-Usually, you should be able to import Bitwarden exports directly into ente
|
|
|
|
|
|
+Usually, you should be able to import Bitwarden exports directly into Ente
|
|
Authenticator. In case this didn't work for whatever reason, I've written a
|
|
Authenticator. In case this didn't work for whatever reason, I've written a
|
|
-program in Python that converts the JSON file into a TXT file that ente
|
|
|
|
|
|
+program in Python that converts the JSON file into a TXT file that Ente
|
|
Authenticator can use, so you can try importing using plain text import instead.
|
|
Authenticator can use, so you can try importing using plain text import instead.
|
|
|
|
|
|
You can download my program
|
|
You can download my program
|
|
@@ -140,18 +140,18 @@ To run the Python program, open it in your IDE and run the program, or open your
|
|
terminal and type `python3 authy_to_ente.py` (MacOS/Linux, or any other OS that
|
|
terminal and type `python3 authy_to_ente.py` (MacOS/Linux, or any other OS that
|
|
uses bash) or `py -3 authy_to_ente.py` (Windows). Once you run it, a new TXT
|
|
uses bash) or `py -3 authy_to_ente.py` (Windows). Once you run it, a new TXT
|
|
file called `auth_codes.txt` will be generated. You can now import your data to
|
|
file called `auth_codes.txt` will be generated. You can now import your data to
|
|
-ente Authenticator!
|
|
|
|
|
|
+Ente Authenticator!
|
|
|
|
|
|
---
|
|
---
|
|
|
|
|
|
You should now have a TXT file (method 1, method 2.1) or a JSON file (method 2)
|
|
You should now have a TXT file (method 1, method 2.1) or a JSON file (method 2)
|
|
-that countains your TOTP secrets, which can now be imported into ente
|
|
|
|
|
|
+that countains your TOTP secrets, which can now be imported into Ente
|
|
Authenticator. To import your codes, please follow one of the steps below,
|
|
Authenticator. To import your codes, please follow one of the steps below,
|
|
depending on which method you used to export your codes.
|
|
depending on which method you used to export your codes.
|
|
|
|
|
|
-## Importing to ente Authenticator (Method 1, method 2.1)
|
|
|
|
|
|
+## Importing to Ente Authenticator (Method 1, method 2.1)
|
|
|
|
|
|
-1. Copy the TXT file to one of your devices with ente Authenticator.
|
|
|
|
|
|
+1. Copy the TXT file to one of your devices with Ente Authenticator.
|
|
2. Log in to your account (if you haven't already), or press "Use without
|
|
2. Log in to your account (if you haven't already), or press "Use without
|
|
backups".
|
|
backups".
|
|
3. Open the navigation menu (hamburger button on the top left), then press
|
|
3. Open the navigation menu (hamburger button on the top left), then press
|
|
@@ -159,9 +159,9 @@ depending on which method you used to export your codes.
|
|
4. Select the "Plain text" option.
|
|
4. Select the "Plain text" option.
|
|
5. Select the TXT file that was made earlier.
|
|
5. Select the TXT file that was made earlier.
|
|
|
|
|
|
-## Importing to ente Authenticator (Method 2)
|
|
|
|
|
|
+## Importing to Ente Authenticator (Method 2)
|
|
|
|
|
|
-1. Copy the JSON file to one of your devices with ente Authenticator.
|
|
|
|
|
|
+1. Copy the JSON file to one of your devices with Ente Authenticator.
|
|
2. Log in to your account (if you haven't already), or press "Use without
|
|
2. Log in to your account (if you haven't already), or press "Use without
|
|
backups".
|
|
backups".
|
|
3. Open the navigation menu (hamburger button on the top left), then press
|
|
3. Open the navigation menu (hamburger button on the top left), then press
|
|
@@ -172,7 +172,7 @@ depending on which method you used to export your codes.
|
|
If this didn't work, refer to
|
|
If this didn't work, refer to
|
|
[**method 2.1**](#method-21-if-the-export-worked-but-the-import-didnt).<br><br>
|
|
[**method 2.1**](#method-21-if-the-export-worked-but-the-import-didnt).<br><br>
|
|
|
|
|
|
-And that's it! You have now successfully migrated from Authy to ente
|
|
|
|
|
|
+And that's it! You have now successfully migrated from Authy to Ente
|
|
Authenticator.
|
|
Authenticator.
|
|
|
|
|
|
Now that your secrets are safely stored, I recommend you delete the unencrypted
|
|
Now that your secrets are safely stored, I recommend you delete the unencrypted
|