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.

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

    I personally love keeweb. Passwords and 2fa all in one place.

    I mean you could argue that defeats the purpose of having 2fa, but it’s convenient

    • @technojamin@lemmy.world
      6•2 years ago

      It weakens it a bit, but in my opinion it still has strength where it counts. If an attacker gets access to your password outside your password manager (man-in-the-middle, keylogger, phishing), then you’re still protected. Maybe it’s hubris in my own ability to keep my password manager safe, but I’ve never been worried about storing MFA in my password manager.