Raising the bar for software security: GitHub 2FA begins March 13
github.blog
On March 13, we will officially begin rolling out our initiative to require all developers who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA) by the end of 2023. Read on to learn about what the process entails and how you can help secure the software supply chain with 2FA.

I personally am fine with this.

  • @subtext@lemmy.world
    7•2 years ago

    Well the good news for you is that a website specifying one or the other is nothing more than marketing from that app maker! So long as there is a QR code (or a long random-ish string), you can use any authenticator app that supports that website’s 2FA algorithms!

    That last bit is important because I think Lemmy had a non-standard 2FA algorithm (SHA-256?) that wouldn’t work with Google Authenticator.

    • Otome-chan
      1•2 years ago

      that’s good to know. I’ll just switch everything over to google authenticator then.

    • RootiestEnglish
      6•2 years ago

      Lemmy works with Google Authenticator, but not with Authy.

      Annoyingly Authy fails silently and ignores the part of the code that specifies SHA-256 and just generates a SHA-1 code that won’t work with no warning or indication to the user.