Live data from Hacker News

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

github.blog

51–60 of 90 posts

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

#51
post #22
post #7

Earlier quoted context omitted.

In what way? Morally and ethically, I think you're going to get a resounding yes from people here. Legally, I very much doubt it, but I am not a lawyer.

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

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

#52
post #12

Absolutely insane. Why does Github even care whether I use 2FA?

It looks like it's for accounts that contribute code. Compromised accounts can sneak malicious stuff into dependencies.

Maybe I don't understand what "contribute code" means... Do I only "contribute code" if I open a PR on a repo I don't own? Seems like a good option to allow people to enable, but forcing it is an unnecessary overreach.

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

#53
post #22
post #7

Earlier quoted context omitted.

In what way? Morally and ethically, I think you're going to get a resounding yes from people here. Legally, I very much doubt it, but I am not a lawyer.

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.

I’m not sure what the laws are, but it would seem pretty silly to fire an engineer over the cost of a device like this. Of course it is important that you don’t have a cellphone, from your employer’s point of view.

Or “I don’t bring it to work, I want to focus on your issues 100% no distractions, boss :)”

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

#54
post #49

Earlier quoted context omitted.

If you already have unique, long, random passwords, I'm guessing you're using a password manager? Why not use the password manager for the 2FA as well? Obviously, if your password manager gets broken into, you're fucked. But if the site only have the issue of exposing passwords, you'll be safe.

> Why not use the password manager for the 2FA as well? Why suggest an extra step to them if they're claiming it's unnecessary? Can you at least try to explain why you think it adds value?

> Can you at least try to explain why you think it adds value?

I thought I already did? "But if the site only have the issue of exposing passwords, you'll be safe." is not clear enough?

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

#55
post #36

The code I upload to github is not part of "the software supply chain". Adding 2fa makes it more likely that I will lose access to my account. There is no way I'm going to participate in this. I'm especially not giving github my phone number or in any way associating my mobile device with their website.

2FA != associating your mobile device. There are numerous devices you can use for TOTP 2FA, your computer, a hardware device and even your browser via authn.

I'm familiar with 2fa. It increases my risk and I'm not using it. I said I'm especially not using my phone. I did not say that 2fa = associating my mobile device.

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

#56
post #41

Earlier quoted context omitted.

I wish the makers of Google Suite thought the same way.

If you are admin of a Google domain then you can disable SMS for 2fa and require either a hardware key or TOTP.

I wasn't aware that was configurable (we were told SMS or Gauthenticator app), I wanted just a OTP code. I'd be delighted if that's really available. I'll chase it up with our admin. Thanks

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

#57
I actually like sms 2fa. It all depends on your threat model of course.

I can lose my authenticator app, printed backup code, my hardware key but I'd still have a way to get access to my account back.

Infact I was on the "sms is unsafe" bandwagon until I nearly lost access to my Google Account.

Never again. Sim jacking is not a real world issue for most people. I'm not special enough that someone, especially someone who has the means to do sim jacking to want access to my accounts.

People do what you are comfortable with, if you are that important, I'm sure whoever wants your stuff will find other ways to get it.[1]

[1]https://xkcd.com/538/

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

#58
post #33

GitHub is also one of the few big sites that support Passkeys for 2FA. You can use your Trusted Platform Module, Yubikey, or any Secure Enclave equipped Mac to 2FA.

> GitHub is also one of the few big sites that support Passkeys for 2FA. Not yet, it seems? "Lastly, we’re already testing passkeys internally, which we believe will combine ease of use with strong, phishing-resistant authentication. Keep an eye on this space for when this functionality is ready for you."

I've just added my 2020 Macbook Air as a security key. It's under "Security keys" in the account security settings [1], just like Yubikeys.

[1] https://github.com/settings/security

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

#59
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...

If you already have unique, long, random passwords, I'm guessing you're using a password manager? Why not use the password manager for the 2FA as well? Obviously, if your password manager gets broken into, you're fucked. But if the site only have the issue of exposing passwords, you'll be safe.

> I'm guessing you're using a password manager? Why not use the password manager for the 2FA as well?

Mostly the built-in Mac keychain, stored locally, no iCloud.

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

#60
I hate the 2FA story, they shouldn't let you enable it unless you enroll at least two different factors. One primary and one for recovery.

The only case where it should be fine to have a single second factor is with your employer, where you have other means to authenticate (i.e. likely your boss knows you and can vouch for you on a 2FA reset).

Also making it mandatory for things that you may really don't care about is overkill.

I would prefer to have ID verification, rather than an anonymous account, for account recovery.

You lose the second factor, and you can re-authenticate by, let's say, making a small payment with a credit card in your name plus some photo id.

Post reply on HN