Text of discuss.python.org › t › disallowing-sms-2fa-for-the-python-github-organization › 1… as Styx crawled it on Nov 20, 2026. The page may have changed since. Only its words are kept, without pictures or layout.

Open the live page

Disallowing SMS 2FA for the `python` GitHub organization - Core Workflow - Discussions on Python.org

Disallowing SMS 2FA for the `python` GitHub organization Core Workflow security sethmlarson (Seth Michael Larson) November 16, 2026, 10:23pm 1 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, WebAuthn, or hardware key). Remove SMS 2FA option from their account, if applicable. “Outside collaborators” are different from GitHub organization members, and will lose access to repositories if SMS 2FA is not removed from their account .

We’re aware that translations repositories members typically contribute with the “outside collaborators” access model and are reaching out to translators before enforcing this new policy (thank you @hugovk ). We’re generating a complete list of outside collaborators to contact ahead of this change and to preserve to short-circuit reinstating access. 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 to do direct outreach. 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. 13 Likes Disallowing SMS 2FA for the `python` GitHub org tjreedy (Terry Jan Reedy) November 17, 2026, 4:23am 2 Could you add links to the GH pages on the alternatives. hugovk (Hugo van Kemenade) November 17, 2026, 5:08am 3 Here’s the top-level page about 2FA: Securing your account with two-factor authentication (2FA) - GitHub Docs How to add 2FA using a TOTP app, a passkey, a security key, and GitHub Mobile: Configuring two-factor authentication - GitHub Docs And you can see your 2FA settings here: github.com/settings/security 3 Likes encukou (Petr Viktorin) November 19, 2026, 8:42am 4 When this topic was posted, a half of the python org members have SMS auth turned on. [1] Now it’s down to a third.

It looks like many people just didn’t turn it off when enabling a more secure method. If that might be your case, you can check your settings page . Next to SMS there should be an “Add” button: image 395×117 12.4 KB That includes some people that liked this topic, who got to beta-test instructions that the others might see soon :‍) ↩︎ 2 Likes Rosuav (Chris Angelico) November 19, 2026, 8:54am 5 Is there a way to find whether someone has multiple 2FA methods registered?

I looked at the GitHub API docs in the hopes of making a simple way to check (give people a nice green check mark “all good” or a warning “you have SMS as well as something else, disable SMS” or a critical “please set up alternative 2FA”), but I don’t think there’s anything more granular than “yes, 2FA is enabled”. REST API endpoints for users - GitHub Docs hugovk (Hugo van Kemenade) November 19, 2026, 11:18am 6 Yes, it’s possible for org owners to see which org members have no/insecure/secure 2FA configured, and we’ll contact them.

1 Like