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

[–] Dymonika@beehaw.org 3 points 3 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.

[–] delirious_owl@discuss.online 2 points 3 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.

[–] Dymonika@beehaw.org 2 points 3 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?

[–] delirious_owl@discuss.online 2 points 3 months ago (1 children)

They are not time based, correct.

[–] Dymonika@beehaw.org 2 points 3 months ago* (last edited 3 months ago) (1 children)

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

[–] delirious_owl@discuss.online 2 points 3 months ago* (last edited 3 months ago)

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