4 ms·
Your decision makes me sad. GitHub is doing something the world needs: putting better security on a huge chunk of the open source software that is shared and r
by xbar 3y ago
Your decision makes me sad.
GitHub is doing something the world needs: putting better security on a huge chunk of the open source software that is shared and relied upon by literally all of humanity.
Any repo, anywhere, has the chance to become a part of the open source ecosystem. Strongly authenticated developer accounts on those repos is critical for everyone's security. It sucks that we are here, but here we are. Password managers are almost enough to save us, but not quite.
I think it is fair to complain about particular factors of 2FA (e.g. TOTP or Yubikey or iPhone Passkey or SMS or whatever). And it's fair to complain that the session timeout on a strongly authenticated persistent session cookie should be user-managed (30 days? no problem! 90 days? I trust my device enough for an API key, why not a cookie?).
And all your command-line stuff is already API key-based on GitHub...
But good 2FA offers real security against a lot of threats. I hope more people embrace it.
- 000ooo000 3y agoAnother commenter below used the phrases high and low value accounts which gets to the crux of why 2FA is a PITA (for me). GitHub is a low value account for me. It's basically Pinterest for code; I track interesting repos, sometimes I raise an issue, and I have dark mode turned on. I have 2-3 garbage private repos that I don't use, so if my account was compromised, it'd be like this: https://media.tenor.com/vJLaS5etgRwAAAAd/shit-wow.gif https://media.tenor.com/vJLaS5etgRwAAAAd/shit-wow.gif It would be like if Reddit started requiring 2FA to 'protect my account'. If I was using GH in a professional capacity, this would be different. But I guess I resent that I don't get to make the choice. Security Daddy at GitHub thinks I'm too stupid.
- deleted 3y ago[deleted]