Live data from Hacker News

Raising the bar for software security: GitHub 2FA begins March 13

github.blog

61–70 of 90 posts

Re: Raising the bar for software security: GitHub 2FA begins March 13

#61
post #6

A quick off topic question related to 2FA. If an employee is required to complete the 2FA to access to the company's system, is the company responsible to provide the employee a necessary device (either phone or hardware token) to complete the 2FA?

You don't need a phone or a hardware token. e.g. https://github.com/rsc/2fa

Re: Raising the bar for software security: GitHub 2FA begins March 13

#63
post #28

I despise 2FA with a passion. Such a PITA. I already use separate, unique, long, random passwords for every site. And I don't even keep them on my phone, just on my desktop. Maybe I should just self-host my few little open source projects...

They're a PITA for a reason, security isn't convenient.

Re: Raising the bar for software security: GitHub 2FA begins March 13

#64
post #28

I despise 2FA with a passion. Such a PITA. I already use separate, unique, long, random passwords for every site. And I don't even keep them on my phone, just on my desktop. Maybe I should just self-host my few little open source projects...

They're a PITA for a reason, security isn't convenient.

Inconvenience isn't security, and no, security doesn't need to be a PITA.

Re: Raising the bar for software security: GitHub 2FA begins March 13

#66
post #17

Earlier quoted context omitted.

We are factoring this into our "should we buy company iPhones for all employees?" conversation right now.

There are much better alternatives than buying a smartphone if all you want to provide is a 2FA device. Yubikey is one alternative, as a consumer you can buy it for ~50 EUR but I'm sure if you buy 100+ for employees, you can get some sort of deal with them.

They sold them for $5 for Ignite. I'm SURE you can get them very cheap if you're buying them in any sort of bulk at all.

Re: Raising the bar for software security: GitHub 2FA begins March 13

#67
post #51
post #22

Earlier quoted context omitted.

Legally. In my opinion, if something is required for a worker to finish the job, the employer is obligated to provide it for free. I could be wrong. Curious to know other people's thought.

Legally you would be wrong. See the entire food delivery industry

I don't see many jurisdictions where food delivery drivers are employees.

Re: Raising the bar for software security: GitHub 2FA begins March 13

#68

> Enroll second factors. Having more accessible 2FA methods is important to ensure that you always have access to your account. You can now have both an authenticator app (TOTP) and an SMS number registered on your account at the same time. While we recommend using security keys and your TOTP app over SMS, allowing both at the same time helps reduce account lock out by providing another accessible, understandable 2FA…

Allowing account access with 2fa code alone is not 2fa, so I guess this feels like a made-up concern.

Re: Raising the bar for software security: GitHub 2FA begins March 13

#69
post #62

The average phone insurance where I live costs a 20% premium per annum relative to the value of the device due to the frequency phones are stolen. What happens when my phone is eventually stolen? I must now depend on the goodwill of morose carriers?

Don't use your phone as a 2FA then?

Re: Raising the bar for software security: GitHub 2FA begins March 13

#70
I gotta say, I don't believe most people here. When it comes right down to it, learning the habit of plugging your yubikey in when you sit down, is much easier than switching git hosting providers and all associated migrations that might not even ... Be possible outside the GitHub ecosystem.

I say this as someone with intentions to leave GitHub, but that has more to do with them ruining nixpkgs contribution history by MAKING ENTIRE ISSUES AND PULL REQUESTS UNVIEWABLE because a single banned user participated in them years ago. Love you GitHub, brilliant.

Post reply on HN