-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Proposal: enforce 2FA requirement for Org members and collaborators #12209
Comments
Re-enabled 2FA. Thanks for the notification. |
Enabled. |
I definitely support this, as soon as everyone has it enabled. We haven't had a breach (that I know of) yet, but we can never be too careful. We could consider what to do for people who don't reply on a case-by-case basis e.g. after 1 month. |
Hi every one. |
Feel free to drop me :) |
Enabled. |
Update: It's been a month and only 2 more people are yet to respond, I will try contacting Edit (11/03/24): Sent a mail to @quantumflo informing them about this. |
I'm sorry, I had some exams in my college this week, so I haven't checked anything from Github. I've enabled 2FA now. |
@sbrl only one more person (@quantumflo) is yet to respond (I sent an email and tried contacting them through other means a few days ago but to no avail). IG we can enable this setting (and update MAINTAINERS.md). We can always reinvite them back when they respond in future. What do you think about this? |
@kbdharun |
Almost enabled the setting where I noticed a new name which didn't appear in both the lists (under the query but just normally), no idea why (their 2FA status was marked with a clock so I suspect they recently disabled it). @Geipro (previously @Proscream) can you enable 2FA for your account? Will wait till this weekend to enable this fully and update the |
Update: I have enabled the setting now and the 3 collaborators have been removed (will update |
Continuing #11918 (comment). (cc @sbrl)
I want to propose enabling two-factor authentication (2FA) at an organisational level for all members and outside collaborators to have better operational security (OPSEC) at tldr. This would prevent unauthorized access to the repositories and clients at Org in case the maintainer's credentials are leaked/their device is compromised.
Since we are a decentralized organization, it is essential to implement basic OPSEC practices like 2FA, private vulnerability reporting, etc. We already have some practices in place, 2FA would be the recent addition to it, GitHub is actively requiring accounts to enable 2FA, so you would want to enable it nonetheless.
The following users don't have 2FA enabled for your account, I would like to request you guys to enable it soon (to prevent being automatically removed when enabling the setting in future).
Org Members:
@isaacvicente(Enabled 2FA)Outside Collaborators:
@CairnThePerson(Enabled 2FA)@Managor(Enabled 2FA)@MrMw3(Enabled 2FA)@patricedenis(Enabled 2FA)@quantumflo(Enabled 2FA)@rubenvereeckenrequested to be removed from the tldr-pages organisationYou can enable two-factor authentication here -> https://github.com/settings/security
Reference links/settings
https://github.com/organizations/tldr-pages/settings/security
The text was updated successfully, but these errors were encountered: