You are reading a single comment by @aggi and its replies. Click here to read the full conversation.
  • BitWarden https://bitwarden.com/ is the one I swear by currently. Open source, all platforms.

    For 2FA apps, on Android I now swear by Aegis https://getaegis.app/ ... but mostly because it works and it enables import / export and my 2FA secrets would be hellish to reproduce so being able to back them up within my control is great.

    For VPN it depends what you want one for... but if privacy / security then https://mullvad.net/en/ are the only game in town (that has actively stood up for the principles by which they claim to operate). If it's for pure geolocation detection avoidance for things like Netflix... I dunno, I don't do that so I'm not sure if this is a fit for that.

  • I seem to remember you used to use Authy but had some issues. How did you export from Authy to Aegis, I can't see an option and I assume setting them all up again would be an absolute ballache (or is that what prompted the move)?

  • How did you export from Authy

    I researched a load of approaches and it can be reduced to this:

    1. You need to export the secrets behind the tokens
    2. You can either do this via JavaScript within the web based version of Authy (the extension) or by communicating with Authy and unlocking and reading the vault of secrets.

    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.

About

Avatar for aggi @aggi started