You are reading a single comment by @aggi and its replies.
Click here to read the full conversation.
-
Cheers, much easier than the other options of Chrome developer consoles and the like.
Only one of my codes didn't import correctly and I have no idea what that was for as I can't find a matching login. No editing was needed. All my codes are 6 digit (bar the one that didn't import correctly) so I'll give it a brief test but think I should be good to move.
I researched a load of approaches and it can be reduced to this:
I found the web based extension never listed all of my accounts... so whilst this is the most documented approach it didn't work for me.
But... I stumbled upon this https://github.com/alexzorin/authy which is written in Go and was effortless to run, and it perfectly exported every secret from the Authy vault (by communicating with the Authy servers).
Once I had the export, I had to then test whether the secret worked in Aegis... when I proved a couple produced the same value (by manually importing them via taking the secret and dropping it into a QR generator... the secret looks like a URL)... then I did an export from Aegis, looked at the differences between what was exported by the tool and what Aegis expects... I edited the export to match Aegis (very minor changes), and then imported the entire export as if Aegis had exported it.
The import / export file is basically a single secret (looks like a URL) per line. So it's really simple.
This entire thing took about an hour, and most of that was me choosing to manually verify every TOTP token that was generated.
At the end... I uninstalled (but didn't close the account) Authy. If you have any Authy 7-digit codes you need to not close your account as it will invalidate the token on their side. If you only have 6-digit codes then feel free to close the Authy account.
But that's it... and now, whenever I add a new TOTP to Aegis, I export afterwards and I keep the export safe.