Mandatory GitHub 2FA is a bad idea. #63813
Replies: 59 comments 85 replies
-
I'm a hobby game programmer, I've deleted all my repos and will abandon the platform over this. |
Beta Was this translation helpful? Give feedback.
-
I use a Yubikey-based secured key (WebAuthn compatible security key) and it works well. You just have to go to https://github.com/settings/security and set up your security key.
For TOTP you can use KeypassXC which is free and open source and works offline. If the problem is the GitHub suggestions, I think GitHub can improve that easily. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
Gitlab.com is also much better in such aspects. In developer community you can meet guys who has absolutely different experience and skills, including professionals and each one decide himself how to secure his account. Github should provide tools and may only recommend but not make so much pressure. Thank you, but - no! Fck u Nvidia, fck u GitHub. |
Beta Was this translation helpful? Give feedback.
-
Obligatory 2FA is very bad idea. I don't want to spend my time for 2FA. I'm not going to spend my time to touch a mobile phone to read messages. |
Beta Was this translation helpful? Give feedback.
-
I was able to use my Solokeys, which are Free as in Freedom. But, it was more of a pain than necessary because Github kept prompting me to set a PIN. I do not use Microsoft Windows, so I do not need a PIN on my 2FA keys. I had to work around it by setting security.webauthn.ctap2 to False in Firefox's advanced preferences (about:config) . To people who are considering deleting their accounts here: Please don't. Please instead mark the repository as archival with a link to your new home. Thanks! |
Beta Was this translation helpful? Give feedback.
-
Completely agree. This is a horrible idea PLEASE reconsider github. Phone breaks, gets stolen, or you are in another country without cell service, and all of a sudden you are unable to access anything. |
Beta Was this translation helpful? Give feedback.
-
Today I got a notification about enforced 2FA on GitHub. Microsoft threatens to lock me out of all my work if I don't enable 2FA by October. If this decision is not reversed, I will be deleting all my repos and abandoning this platform in the near future. |
Beta Was this translation helpful? Give feedback.
-
"2FA is significantly more secure" "2FA" is more control - it is as simple as that; this is how their mandatory "2fa" sounds to me: "you should have smartphones or you're not good enough for our service" - a certain sentence towards a certain machine at the end of the movie "Oblivion" comes to mind; my POV. Also, imagine the bonus pressure on all employees who have to maintain "2fa" phone(s). Anyways, its part of their contract: they can do whatever they like whenever they want; their service - their rules. What was promised was given - a choice was taken away. Yay "2fa"! |
Beta Was this translation helpful? Give feedback.
-
I have no doubt that this is coming from Microsoft. They always envied Google for their abundant amount of user data, but could never get even close with all the failed Bing iterations. But they are learning from Google who have perfectioned their ways of asking for user consent to process their data right in the moment (of setup or configuration wizards) when users' interest and will for dealing with the subject of those consents is down to a minimum. And so, the big players came to the ingenious idea to require mobile phone verification for registration of accounts and using services. It's a clear and simple way to make users more identifiable: while users often have multiple e-mail addresses, they rarely have multiple phone numbers. And what's the most convincing rationale for why this would be required? => Just like Google does it all the time: Tell that this is crucial and important for the user's safety and account security. Bravo, Microsoft! You learned a lot from Google. But it's still unacceptable. |
Beta Was this translation helpful? Give feedback.
-
Guess I'll have to say "bye bye" on oct 12. |
Beta Was this translation helpful? Give feedback.
-
Hey User!Give us access (or number) to your smartphone! Otherwise we will delete all your data.github.com |
Beta Was this translation helpful? Give feedback.
-
This is ridiculous in so many ways (not 2FA per-se, but: 1. the forcing and 2. the available options and 3. the context). By "context", I mean the fact that the token-based authentication for build automation or application access does not change. A major advantage of tokens (like PAT) is the ability to segment access by permission and by target usage, but besides that (and expiration), this is not much better than a login with username and (strong) password. Neither Visual Studio nor my other Git application are caring about segmentation. Maybe it's possible in some way, but by default, they are setting up a token with full access rights. when you go through the process. The outcome of this would be that Visual Studio and other Git applications are able to log on to GitHub always and easily, but I-for-myself would need to jump through dozens of hoops just in order to log in to GitHub When something goes wrong, my applications would still be able to log in to my GitHub account, even though mine would have been cut off and inaccessible I also don't understand the general idea of how an application should be more secure when dealing with passwords. For every application it is known where it stores passwords and once a security hole has been found to crack the storage encryption, it can likely be exploited everywhere where the application is installed. But when I'm in charge, nobody will know where I might store my passwords, or I even might just memorize the crucial ones. This is something that cannot be hacked like an application can be. Eventually, it is MY account and ONLY MY account. That means that I (alone) need to be in charge of logging in. It is not acceptable that my powers and capabilities (to log in) are transferred to or shard with an application or a mobile phone into which I do not have any insight or control. |
Beta Was this translation helpful? Give feedback.
-
UPDATE: It has been pointed out to me that GitHub now requires your SMS phone number in order to register a FIDO2 key! Argh, Microsoft...I have opened a bug report on the GitHub general forum. Original post follows... 2FA AnonymityI see a lot of people saying exactly what I was thinking: they want anonymity and don't want to give their cell phone information out. There is a workaround, but, amidst this boneheaded decision, Microsoft is not making it obvious that: You can use a USB security key for 2FAJust search for "FIDO2" and "USB" and you'll find lots of brands to choose from. Here is a sample: Yubico (~$25) is well respected and trusted. Made in the USA or Sweden. Yubico is what Google gave to their employees before they came out with their own Titan key (~$35) (China). Personally, I've been only buying from Solokeys (~$20) because they publish the blueprints for their designs under an open source license, which is the ideal from a security perspective. Made in Italy. If cost is an issue, try Adafruit's $10 Key, made by Key-ID in China. Buy twoOne important thing to know is that you have to buy at least two 2FA keys. Think of them like the keys to your home or car: if you don't have a backup, you will be screwed when you lose the primary one. Mandatory 2FA is still a bad ideaI think 2FA is a great idea for security, but it shouldn't be mandatory. It is driving away developers, particularly the individuals who were doing cool projects on their own time. This is going to change the culture of GitHub, tilting it more corporate. Maybe that's for the best as Microsoft's ethos and interests are not well aligned with the open source community and it has been uncomfortable to see so many open source projects existing at the pleasure of a behemoth corporation. |
Beta Was this translation helpful? Give feedback.
-
What if I don't have bluetooth? I tried using passkeys with Google, not working because it requires some crappy bluetooth setup. |
Beta Was this translation helpful? Give feedback.
-
I agree, |
Beta Was this translation helpful? Give feedback.
-
I do not remember delegating Microsoft or any corporation to make decisions like that on my projects. They did not become a custodian of how we make decisions on our projects and they do not have the right to make dictates like this to us. This should be an opt in/out process. |
Beta Was this translation helpful? Give feedback.
-
How about more security? Micro$oft?
|
Beta Was this translation helpful? Give feedback.
-
i think this is because israel |
Beta Was this translation helpful? Give feedback.
-
If I want to be "less secure" LET ME |
Beta Was this translation helpful? Give feedback.
-
I'm concerned about GitHub's decision to enforce mandatory 2FA without prior consent, potentially locking users out of their accounts. While security is crucial, this approach raises suspicions about GitHub's intention to take undue ownership of users' code repositories. It's vital to ensure that security measures empower users rather than restrict their access to their own code. |
Beta Was this translation helpful? Give feedback.
-
Hey, thanks so much man for mentioning codeberg. I'm also migrating from GitHub and doing the same thing, pulling out and down all of my repositories since I won't be using their stupid 2FA. So sick of this F2A bs. Never thought GitHub would fall under but oh well. I just know since I won't be using it then I'll be locked out of my GitHub account, they honestly should have made this optional instead of losing a bunch of users. |
Beta Was this translation helpful? Give feedback.
-
#1 |
Beta Was this translation helpful? Give feedback.
-
2FA has its place, but if you argue that it is because your users are too dumb to manage their passwords appropriately is completely disrespectful and does not shine a positive light on you. Who are you to tell me that I am too dumb to use your service correctly? You, who are responsible for more major data leaks and security breaches than I could ever produce, even if I WERE as dumb as you think. So stop disrespecting your users. Give them options and allow them to live with their choices. Compare your users' track records in security to your own, before you patronize them. |
Beta Was this translation helpful? Give feedback.
-
I do not want to make the effort of 2FA for my little, non-critical project. 2FA can make a lot of sense for bigger projects or projects that where control over it has significant value, but not for my. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
Ditto. I've been a dev for 25 years. You know what's on my github account? Random nonsense scripts I'm playing with. I would give ZERO f's if my github account was hacked, and it has a completely unique 20 character password that is managed by a password manager. I often take my laptop and head to a cafe to work for a while. I almost never carry my phone because I like being otherwise detached when I'm walking around. Not being able to log into github from a coffee shop is ridiculous. You are not a bank. There is ZERO tangible value in open source code. Plenty of people see value in it, I 100% understand that. Let them opt in, or at least let other people opt out. Any site requiring 2FA where money is not involved is absolute BS. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Mandatory 2FA is a bad idea. Please reconsider that decision.
SMS-based 2FA is so bad that I don't even know why GitHub supports it. This change is going to result in a lot of people being made vulnerable to a SIM swap attack.
Additionally, the authenticator apps GitHub gives as examples are all proprietary - none of them are free (as in freedom) software.
I don't like GitHub itself being nonfree, and I REALLY don't like them pushing nonfree native apps.
I use CSRNG-generated website-specific passwords that are only ever stored locally. TOTP has no security benefit since an attacker would be on the same machine anyways.
Using FIDO2 security keys is the only right way to do 2FA, but
GitHub currently doesn't even support it. (EDIT: it appears that GitHub does support it after all, hmm...)Also keep in mind that Mojang, which is also owned by Microsoft, did something similar (except in that case it was even worse since they are forcing you to have a Microsoft account) with the reason being security - it's pretty clear that was nothing more than an excuse, and the real reason is to tie products and make more money.
This annoyance is what has caused me to finally migrate off of GitHub. I'm moving all of my projects to codeberg and I'm probably going to delete them from GitHub so they can't get a higher SEO ranking for my projects.
By the way, I've posted about this on the fediverse too: https://mastodon.social/@hexaheximal/110890236595013160
Beta Was this translation helpful? Give feedback.
All reactions