News for hackers. Stuff that matters.
Re:Leaving GitHub by dale_glass on Monday September 04, 2023 @10:18AM (#37380707)
2FA is an odd thing to have a problem with.

Open source today is absolutely security critical. If you have commit access to something like say, libjpeg or some other such widely used component, you make a very, very juicy target for attackers.

And it's hard to tell whether you are in such a category. You may not know that your small tool library happens to have made it into some big software product.

Also, Github's 2FA doesn't require SMS. You can use Google Authenticator just fine. It's just a secret obtained by scanning a QR code, your phone number is not involved. Yubikeys and similar are also supported, as well as authentication via the mobile app.

Re:Leaving GitHub by meandmycode on Monday September 04, 2023 @10:23AM (#37380762)
Exactly, the phone number thing is quite an illogical jump.. I think the author has a problem with Microsoft more than anything - I can't help but think you'll enjoy life more by not looking to be outraged, all the best to this individual.
Re:Leaving GitHub by rhdunn on Monday September 04, 2023 @10:24AM (#37380775)
I'm using the Yubico Authenticator with a Yubikey on Windows, so you don't even need phone-based authentication. Yes, you do need a yubikey for these to work, but I prefer that to handing out my phone number to these 2FA services.
Re:Leaving GitHub by mxmlnkn on Monday September 04, 2023 @10:25AM (#37380780)
The mention of phone numbers also confused me. You can even store the secret, which shows besides the QR code, somewhere else and use oathtool --totp --base32 to generate tokens without a smartphone.
Re:Leaving GitHub by follower on Monday September 04, 2023 @11:23AM (#37381367)
It took me a non-zero amount of time researching to discover all that--it's not like the GitHub information spells that out as an option.
Re:Leaving GitHub by mxmlnkn on Monday September 04, 2023 @01:55PM (#37383069)
That is true and I mentioned oathtool in order to spread my knowledge. At least this trick can be used for almost any 2FA method.

And, more and more keep bothering me with this, e.g., when trying to read Google mails via Thunderbird, you have to create 2FA in order to create an application token that can be used with Thunderbird. So many tokens and passwords. It really keeps getting on my nerves and I don't trust things that are locked onto my smartphone because it might get lost. The first reflex was to simply save the QR code, but then I also wanted to know how I could use it without Google authenticator and so I found oathtool. And as can be seen from the two necessary command line arguments, the default oathtool invocation also didn't work out of the box.

To be fair, Google and also Github, both, provide recovery codes, which can be used if you loose your 2FA device. But now you have basically 3 "passwords", two Yubikeys, plus your associated mail address, all of which you have to remember or store. All of this just for a single account out of a thousand, which you aggregate over a decade or more.

Re:Leaving GitHub by follower on Monday September 04, 2023 @11:51AM (#37381651)
> 2FA is an odd thing to have a problem with.

The author explicitly states in the post that that is not the issue:

"I have nothing against the concept of 2FA. I voluntarily use it elsewhere. That’s not what this is about."

Re:Leaving GitHub by dale_glass on Monday September 04, 2023 @01:29PM (#37382743)
It's not really clear what their actual problem is. There are two points being mentioned, collecting phone numbers (which is false, can be done without), and a misunderstanding of the whole protecting consumers motivation.
Re:Leaving GitHub by vvoyer on Monday September 04, 2023 @10:21AM (#37380745)
tl;dr;

- GitHub now requires 2FA

- Author reaction "Greaaaaaat, Microsoft wants to harvest more phone numbers."

- Author has a love/hate relationship with GitHub since 2012

- Author decides to not use GitHub anymore

I am not following the thinking process. And you can use a 2FA app, without giving your phone number to GH.

I can understand the stream of changes at GitHub does not resonates with the author opinions, but the "Microsoft wants phone numbers" is wrong I think.

Re:Leaving GitHub by politelemon on Monday September 04, 2023 @11:54AM (#37381670)
I think you're right. It is trivial to just use an app of your choice, like aegis, authy, even password managers come with 2fa capabilities.

I have to wonder if the author is deliberately misrepresenting 2fa to justify leaving, since they claim to understand it well.

Re:Leaving GitHub by zzzeek on Monday September 04, 2023 @10:24AM (#37380776)
it seems like this person's issue with 2FA is that Github's rationale is to protect the software supply chain, which is consumed by millions including large corporations. The writer is offended by the notion of being asked to do something that might be helpful towards the community that includes corporate consumers:

> Independent FOSS developers do not owe anything to companies, including the slightest effort to "secure the software supply chain" for "consumers." As the licenses say, THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND …

Right, the warranty has no protection against "the software also may be compromised by third parties and contain all kind of backdoors and exploits, which is also not my problem"

I'm sure Github is sad to see such contributors leave !

Re:Leaving GitHub by codemusings on Monday September 04, 2023 @10:31AM (#37380829)
Two things:

1. 2FA does not require your phone number.

2. If you don't already, you should use a public key for pushing your commits

It's highly unlikely that you lose commit access even if you don't complete the "enrollment" unless you use http authentication for pushing commits in which case you should realize that password security is a huge liability for any big web application and I recommend you reconsider your approach.

Re:Leaving GitHub by follower on Monday September 04, 2023 @11:34AM (#37381485)
> highly unlikely that you lose commit access even if you don't complete the "enrollment"

This statement does not appear to be correct.

According to the roadmap graphic[0] (that has no useful accessibility alt text) it says 7 days after deadline "Blocked from accessing GitHub features until you enable 2FA".

[0] https://github.blog/2022-12-14-raising-the-bar-for-software-...

Re:Leaving GitHub by codemusings on Tuesday September 05, 2023 @09:15AM (#37391191)
Sure, but are basic git operations the same as Github features (PRs, Code Review, Actions, etc.)? In any case. Leaving Github in defiance of 2FA requirements seems ill-conceived.
Re:Leaving GitHub by aseipp on Monday September 04, 2023 @10:32AM (#37380831)
> As someone who has been in the industry for the last two decades, you know what my first thought was when I saw this requirement? It was, "Greaaaaaat, Microsoft wants to harvest more phone numbers."

You don't need a phone number for TOTP, which is by far the most popular and widespread 2FA method outside SMS, as well as being very simple from a conceptual and algorithmic point of view. And if you're paranoid but you can't read, understand, and implement RFC 6238 in an afternoon in your own code, you aren't qualified to talk about anything related to 2FA or computer security pretty much at all. Sorry for being a hater, but as someone who spent years of my life in the infosec world writing exploits, listening to the average computer programmer talk about "security" like this is embarrassing.

Re:Leaving GitHub by gray_-_wolf on Monday September 04, 2023 @10:40AM (#37380914)
I wonder why my Advent of Code repositories need a "supply chain security". I do not think it is nice to mandate this. Not every repository is kubernetes. Would have been better to leave it as a per-repository setting.
Re:Leaving GitHub by lemper on Monday September 04, 2023 @10:59AM (#37381102)
ok, friend. take care. and just to prevent any hard feeling, like others have posted, I didn't put my phone number for 2fa. I use yubikey thing (the blue one) and it works just fine.
Re:Leaving GitHub by thelastknowngod on Monday September 04, 2023 @11:15AM (#37381285)
Ok.
Re:Leaving GitHub by follower on Monday September 04, 2023 @11:17AM (#37381308)
I'm glad that someone had the energy to write about this because it bothered me too.

First, with regard to comments re: SMS & phone numbers, it required a non-zero amount of research to discover that GH no longer requires or recommends use of SMS--so it's not unreasonable to not know this.

Second, there are a long list of issues that I have with both the policy & its roll-out but they can be summarised as "different people have different risk profiles" & "in this situation individual developers (the people whose free labour GH was built on) have the least amount of power".

There's a distinct lack of nuance in the implementation/roll-out & 2FA is being used as a blunt weapon because it's easier than accommodating individual developers needs.

At this current point in time the group of people affected is "all users who contribute code"[0] but it's presumably not--it's actually developers who have contributed code. There's no option to keep one's account & use it only for e.g. issue creation/commenting going forward.

(Also, it seems doubtful that this requirement is actually limited to people who "contribute code" but rather seems likely to also include people who "contribute" text files.)

Yes, security is important but it's also always a trade-off. Why isn't it up to individual projects to decide whether to only restrict code contributions to those people with 2FA?

The language used in communication about the changes is also twee[1] (for lack of a better word) and downplays the reality of the situation which is that if you don't enable 2FA or if you enable 2FA and then get locked out of your account you will lose access to the account & history--especially the "non-code" features.

At least on the main docs[2] it's more straight-forward about the situation.

If you don't understand what the problem is then, congratulations, you're probably not one of the people whose first thought in this situation is "if I enable 2FA there's a non-zero chance that in the future I'm going to lose access to all the possible account recovery methods". Which means you probably don't feel at risk of becoming homeless, don't have ADHD or exist in a myriad of contexts where such concerns do exist.

Did MS/GH consult with any disability/inclusiveness specialists when implementing the policy?

Also, the impact isn't just limited to GH when projects like Rust's crates.io also use GH for authentication.

[0] https://github.blog/2022-12-14-raising-the-bar-for-software-... Although in another place it says "active contributors" <https://github.blog/changelog/2022-11-21-updates-to-the-two-...>.

[1] "...it’s easy to start fresh with a new GitHub.com account and keep that contribution graph rightfully green." https://github.blog/2023-03-09-raising-the-bar-for-software-...

[2] https://docs.github.com/en/authentication/securing-your-acco...

Re:Leaving GitHub by voussoir on Monday September 04, 2023 @02:42PM (#37383516)
The mandatory 2FA thing bothered me, but I hooked it up with Aegis, which is FOSS on F-droid, and decided it wasn't the final straw yet. But Github's distasteful AI marketing/desperate pandering is bothering me a lot more. They're advertising Copilot directly on top of my source code. I don't want to be associated with that.

I'm basically a nobody so of course Github doesn't care if I stay or go. But I don't have any investment in their issue tracker or proprietary features because I want to stay nimble and ready to drop GH from my remotes when the time comes.

https://f-droid.org/en/packages/com.beemdevelopment.aegis/

https://i.imgur.com/T2aUA3y.png

https://i.imgur.com/McftJ5H.png

Re:Leaving GitHub by gray_-_wolf on Tuesday September 05, 2023 @06:53AM (#37390112)
I wonder if the end goal here is to mandate M$soft authenticator, with all the telemetry. Given this is Microsoft we are talking about here, I would not rule that out.