Disallowing SMS 2FA for the `python` GitHub organization

In 2022 the Steering Council announced a new policy requiring 2FA for all committers.

Sometime in 2024, GitHub added support creating an org-wide policy to disallow insecure 2FA methods like SMS. I’m proposing requiring non-SMS 2FA across the python GitHub organization using such a policy.

Concretely after this policy is enabled this would mean that some python GitHub organization members would need to take action before being able to interact with python organization resources:

  • If one isn’t already in place: add a non-SMS 2FA option to their account (TOTP, GitHub app, or hardware key).
  • Remove SMS 2FA option from their account, if applicable.

GitHub accounts without SMS 2FA would not need to take any action in this case, as we are already requiring some form of 2FA for the python GitHub organization. I’ve asked a GitHub admin to query the number of affected members for a rough estimate of how disruptive this change would be and whether we’d need to do more direct outreach to folks.

Thanks to @hugovk for pointing me to this feature. I’ve asked the SC to review this proposed change and the SC replied in support.

9 Likes

Could you add links to the GH pages on the alternatives.

Here’s the top-level page about 2FA:

How to add 2FA using a TOTP app, a passkey, a security key, and GitHub Mobile:

And you can see your 2FA settings here:

1 Like