• can
    link
    fedilink
    English
    arrow-up
    5
    ·
    5 months ago

    So what did you do?

    • canadaduane@lemmy.ca
      link
      fedilink
      English
      arrow-up
      20
      ·
      edit-2
      5 months ago

      On Android, I replaced Authy with the open-source Aegis app. It’s just as functional, allows exporting, and doesn’t tie your data to your phone number (nor store it on a central system–not sure if Authy does this or not).

    • Contravariant@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      5 months ago

      Use TOTP wherever possible. It’s standardized, and typically can be found somewhere if you keep digging hard enough.

      Plenty of services push their own proprietary systems hard though. Looking at you M$

      • Tryptaminev@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        ·
        5 months ago

        I also find this infuriating. I had a service offer TOTP for authentication. Installed an open source TOTP Aap, scanned the QR and voila.

        The service meanwhile can control whether they want to generate a new token or give out the old one again, for instance when a device was lost.

        It is the most easy, most convenient solution both for the service provider and the client. There is no excuse for any other 2FA system to be used.