Aegis: Unable to import from Authenticator Plus

Created on 2 Nov 2020  路  6Comments  路  Source: beemdevelopment/Aegis

Info
  • __Version__: 1.3
  • __Source__: Google Play
  • __Vault encrypted:__ Yes with biometric unlock
  • __Device:__ Pixel 4
  • __Android version and ROM:__ Android 11 Build RP1A.201005.004
Steps to reproduce

Attempt import from local Authenticator Plus database file

What do you expect to happen?

Import succeeds

What happens instead?

An error is reported. Detail indicates a Java FileNotFoundException on Accounts.txt after entering the authplus.db password

Log

```
If applicable, paste the debug log here.
(Couldn't see a log anywhere)

bug

Most helpful comment

I've worked it out....

I assumed from the list of apps displayed when importing that Aegis would open the proprietary authplus.db file (the backup database file created from Authenticator Plus). But it looks like Aegis wants to use the more open .zip file created from the Export function of Authenticator Plus. Specifying that file (which does contain Accounts.txt) makes things work.

The wrinkle I had for anyone else seeing this, is that Authenticator Plus is broken for me on Android 11. Sync via Google Drive doesn't work and neither does the Export feature... which is why I initially didn't try using that file as it was not available to me. Eventually what I did was install Authenticator Plus on an Android 10 device, sync my Authenticator Plus database to that using Drop Box and do the Export from that device, and then moved that .zip file back to my Android 11 device where I have Aegis installed. A bit convoluted, but the end result is good.

All 6 comments

Hmm - I see that I get the same error if I intentionally specify an incorrect master password for the Authenticator Plus database file. The password I originally specified above is correct, when used as the Master Password inside Authenticator plus.

I've worked it out....

I assumed from the list of apps displayed when importing that Aegis would open the proprietary authplus.db file (the backup database file created from Authenticator Plus). But it looks like Aegis wants to use the more open .zip file created from the Export function of Authenticator Plus. Specifying that file (which does contain Accounts.txt) makes things work.

The wrinkle I had for anyone else seeing this, is that Authenticator Plus is broken for me on Android 11. Sync via Google Drive doesn't work and neither does the Export feature... which is why I initially didn't try using that file as it was not available to me. Eventually what I did was install Authenticator Plus on an Android 10 device, sync my Authenticator Plus database to that using Drop Box and do the Export from that device, and then moved that .zip file back to my Android 11 device where I have Aegis installed. A bit convoluted, but the end result is good.

I assumed from the list of apps displayed when importing that Aegis would open the proprietary authplus.db file (the backup database file created from Authenticator Plus).

It's a logical assumption. It'll be more clear in the next release that we're expecting the .ZIP file. See: #601.

I have found out that Authenticator Plus does something funky when zipping the HTML and txt files together.
Simply extract the .zip elsewhere, and rezip just the Accounts.txt (CAREFUL WITH THE SPELLING).

I know a lot of legacy Authenticator Plus users, so will inform them.

Thanks Alex and Michael for this awesome replacement.

@SimonKingZA Thanks for reporting this. The issue you're describing appears to have been introduced in d660fbc6d1aa2facfa5358d38782d92b80cb769f by updating zip4j. I'll submit a PR to downgrade it. See: #664.

I have found out that Authenticator Plus does something funky when zipping the HTML and txt files together.
Simply extract the .zip elsewhere, and rezip just the Accounts.txt (CAREFUL WITH THE SPELLING).

I know a lot of legacy Authenticator Plus users, so will inform them.

Thanks Alex and Michael for this awesome replacement.

Between setting up a virtual Android 10 device in Android studio per @andrmo and this, I was able to successfully move my database to Aegis.

Thanks for the help!

Was this page helpful?
0 / 5 - 0 ratings