Open Source

31122 readers

293 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Posts must be relevant to the open source ideology
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago

MODERATORS

[email protected]

How is everyone handling the 2FA requirement for GitHub? (docs.github.com)

submitted 5 months ago* (last edited 5 months ago) by [email protected] to c/[email protected]

126 comments fedilink hide all child comments

Just wondering what people are using to meet the 2FA requirement GitHub has been rolling out. I don't love the idea of having an authenticator app installed on my phone just to log into GitHub. And really don't want to give them my phone number just to log in.

Last year, we announced our commitment to require all developers who contribute code on GitHub.com to enable two-factor authentication (2FA)...

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 5 months ago (1 children)

"Time-based One-Time Password" literally says nothing about the delivery method. Who said it can't involve remote sending?

And what would you call it, then, SOTP?

Anyway, regardless of the terminology-nitpicking, my point still stands.

[–] [email protected] 2 points 5 months ago (1 children)

The point of being time based is to not send it. That's the whole point. To avoid that vecotor of attack.

[–] [email protected] 2 points 5 months ago (1 children)

Do you think the SMS codes are not time-based on the companies' ends? How are they deriving the digits, then?

[–] [email protected] 2 points 5 months ago (1 children)

They are not time based, correct.

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago) (1 children)

Interesting, I didn't know that. So how do they derive the digits?

[–] [email protected] 2 points 5 months ago* (last edited 5 months ago)

Best practice for a cryptographic nonce is to generate them randomly every time