Aegis 🚀 - Authy import failing to import some tokens `No value for secretSeed`

Just installed Aegis, hoping to get rid of google auth and authy and...same problem.
Rooted phone and all.

Looooooka on 13 Nov 2020

Which services did Aegis fail to import?

alexbakker on 13 Nov 2020

Bitstamp, Binance, Mega.nz, Google, MyHSM a nd many more:

Same error on all of them:

org.json.JSONException: No value for secretSeed

From: Alexander Bakker notifications@github.com
Sent: Friday, November 13, 2020 1:41:33 PM
To: beemdevelopment/Aegis Aegis@noreply.github.com
Cc: Luka looooooka@gmail.com; Comment comment@noreply.github.com
Subject: Re: [beemdevelopment/Aegis] Authy import failing to import some tokens No value for secretSeed (#589)

Which services did Aegis fail to import?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/beemdevelopment/Aegis/issues/589#issuecomment-726743231, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABH3ALKFQY3C4L2NUPIEWT3SPUSP3ANCNFSM4ROPQMVA.

Looooooka on 13 Nov 2020

I just tried to reproduce this, but was unable to. Could you share the file that's being imported (first replace the "decryptedSecret", "encryptedSecret" and any other parts that look like sensitive information)? Filename: /data/data/com.authy.authy/shared_prefs/com.authy.storage.tokens.authenticator.xml

alexbakker on 19 Dec 2020

@Looooooka @alexbakker @netpro2k I ran into the same issue, with "No value for secretSeed" occurring on approximately 2/3 of my services I tried to import. There didn't seem to be any particular rhyme or reason for the errors that really stood out, as they were all 6-digit TOTP. There might be some possible issues with the length of particular seeds, but I haven't had an opportunity to inspect them all in detail.

I ended up just using a root explorer and going into the Authy app folder itself, and copying /data/data/com.authy.authy/shared_prefs/com.authy.storage.tokens.authenticator.xml to my computer. Then I used Notepad++ with the XML tools plugin to escape the characters in the selection, exported the file as CSV, then imported the account logins/seed-value pairs to a KeepassXC database for both a long-term backup and an easier import to Aegis/ Microsoft Authenticator, etc.

If some of this procedure could be automated, I think it would solve this error issue, as well as providing a good way to make an encrypted backup of Authy seeds.

tonyping on 20 Dec 2020

I also got the same issue. I have 2 Nextcloud accounts, one was imported, the other not. After looking into the Authy file, i noticed that all the accounts that could be imported had the accountType "authenticator". All the other ones had other types like "authenticator_red" or "twitter", which i think is a result of changing the icon in Authy.

So i think the importer filters somewhere for "authenticator" and doesn't consider the other types.

EDIT: After manipulating the file and changing the accountType of an entry to "authenticator", it was possible to import that entry in Aegis.

ELT4N1N on 22 Dec 2020

👍1

EDIT: After manipulating the file and changing the accountType of an entry to "authenticator", it was possible to import that entry in Aegis.

+1 on this.

I used a root explorer to copy /data/data/com.authy.authy/shared_prefs/com.authy.storage.tokens.authenticator.xml to the non-root part of my phone's storage, then edited the file to change accountType from "amazon" and "discord" to "authenticator", and the amount of failed entries was decreased by 2 (from 31 to 29). It seems, for now, this'll have to be the workaround.

Thanks, @ELT4N1N, for that tip.

EDIT: Transferred the file to my desktop and edited it to change them all to "authenticator". That completely fixed the problem for me as well. Zero errors.

dalaeance on 1 Jan 2021

Thank you all for following up. The accountType!="authenticator" observation is a good one. I'll take a look at fixing this soon.

alexbakker on 1 Jan 2021

🎉1

I think #652 will fix this issue. Can someone verify this? APK: https://alexbakker.me/u/7l4l6o20ij.apk

alexbakker on 2 Jan 2021

👍1

I did a short test and changed some accountTypes back to something other than "authenticator" and was able to import all entries without any error.

Maybe someone should also test it with an original authy file, i don't have mine anymore.

ELT4N1N on 2 Jan 2021

Works like a charm! Imported all tokens from my original file without issue. The only thing I'd note is that my token for Twitch wasn't imported, but that's an "Authy account", where I get a push notification when I try to log into Twitch.

I'm assuming Aegis can't access those? I could probably fix that by turning off 2FA and re-enabling it as a standard, non-Authy specific token.

-------- Original Message --------
On Jan. 2, 2021, 08:58, Alexander Bakker wrote:

I think #652 will fix this issue. Can someone verify this? APK: https://alexbakker.me/u/7l4l6o20ij.apk

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

dalaeance on 2 Jan 2021

Happy new year everyone

cooper5005 on 2 Jan 2021

@dalaeance Good! Thanks for confirming. Proprietary Authy tokens are stored in a separate file called com.authy.storage.tokens.authy.xml. Aegis should be able to import that as well.

alexbakker on 2 Jan 2021

That's good to know. Thanks for the tip, @alexbakker!

dalaeance on 2 Jan 2021

👍1

Aegis: Authy import failing to import some tokens `No value for secretSeed`

Info

Steps to reproduce

All 14 comments

Related issues