-
-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure 2FA is enabled! #489
Comments
In case it's useful, I write a little script when we were enabling 2FA at work, to check which members of the org didn't have 2FA turned on yet, so I could go and https://github.com/hugovk/github-tools/blob/main/org_users_2fa.py |
What's about Bedevere and Miss Islington? I'm working on triggering the former via GitHub Actions but we still need an account token to work with GitHub REST API. [edit: unless we want to deal with |
@arhadthedev discussion here: python/bedevere#531 |
To note, GitHub has been steadily rolling out 2FA for all users, starting with the maintainers of depended-upon projects a couple weeks ago, and concluding with all users by the end of the year. This will include all of us, so all CPython core team members (Triager, Core Dev, etc) will need to have 2FA enabled by around the end of April to continue using their GitHub account. |
Following @CAM-Gerlach latest comment, is it required that all CPython core team members have 2FA enabled? If so, could this issue close? |
It will soon be required. This at least depends on python/bedevere#569 to resolve python/bedevere#531. |
Using @hugovk's script, there are still 13 team members without 2FA: |
Done |
If these core devs enable 2FA later, they can again merge pull requests? |
Yes, but: If they don't enable 2FA before we require it for the org, they're removed from the org. If they enable within 3 months, we can reinstate them with the earlier permissions/settings. If they enable after that, we can re-add them as if they're a new user.
This isn't necessarily a bad thing, because it can be good for security to remove access when it's not used. And it's not permanent, so can be re-added. |
Are you going to contact them? I know a few of them. |
I did enable 2FA but I guess I didn’t do it right? I will try again today
or tomorrow..
…On Sat, Jul 22, 2023 at 2:59 PM Victor Stinner ***@***.***> wrote:
Are you going to contact them? I know a few of them.
—
Reply to this email directly, view it on GitHub
<#489 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB3RIWXKSZQDBX2PMOL4Q3XRQPH3ANCNFSM6AAAAAAT7TT2YU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
These folks need to be contacted maybe by email before as an example Laura Graves might also lose functionality related to her PSF work unknowingly or she may not be checking and using GitHub actively @LauraGraves . |
I've enabled 2FA now.
…On Tue, Jul 25, 2023 at 7:38 AM Joannah Nanjekye ***@***.***> wrote:
These folks need to be contacted maybe by email before as an example Laura
Graves might also lose functionality related to her PSF work unknowingly or
she may not be checking and using GitHub actively @LauraGraves
<https://github.com/LauraGraves> .
—
Reply to this email directly, view it on GitHub
<#489 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB3RIR7UE75EZBOGGORA3LXR6V5FANCNFSM6AAAAAAT7TT2YU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Reminder that GitHub will "require all developers who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA) by the end of 2023". https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13/ @ambv Who still needs to enable 2FA? |
GitHub now requires 2FA for code contributors. I'll close the issue: there's nothing more to do, and it doesn't look like anyone connected to core workflow is affected now. |
All members of the python organization will soon be required to have 2FA enabled.
Currently some members of @python/python-core and @python/python-triage do not have 2FA enabled.
At your earliest convenience, please go to your account security settings and ensure that the “Two-factor authentication” section shows “Enabled”.
If not, please enable 2FA for your GitHub account according to GitHub's documentation. Be sure to save your recovery codes somewhere safe while doing so!
The text was updated successfully, but these errors were encountered: