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.
    • jana@leminal.spaceEnglish
      0·
      1 year ago

      Print off your recovery codes and keep them safe. If you want to be extra, hammer them into metal plates like the crypto weirdos do.

      • argv_minus_one@beehaw.org
        01·
        1 year ago

        Printing recovery codes would require me to either be price gouged by the printer ink cartel or use someone else’s printer, and using someone else’s printer is begging to get my account stolen.

        I have no idea how to hammer things into metal plates, but I’m guessing that’s even more expensive than printer ink.

          • argv_minus_one@beehaw.org
            01·
            1 year ago

            I can do that with alphanumeric codes, yeah, but can I get alphanumeric codes from GitHub, or is it going to be a QR code? I can’t write down a QR code…

            • faerbit@feddit.de
              0·
              1 year ago

              QR codes are just an encoding. Just use any half-competent QR code app, and it will give you it’s content, which you can then write down. For the reverse you can use any QR code generator.