HackerNews中文版

你好，birdie-github！我们写信通知您，正如去年宣布的那样，我们将正式（[开始][1]）要求 GitHub.com 上某些贡献者启用双因素身份验证 (2FA)。您收到此通知是因为您的帐户符合当前注册组的标准，并且您已启用 2FA。您无需回复此电子邮件。2026 年 9 月 2 日 00:00 (UTC) 之后，您将无法再禁用 2FA。如果您在此之前禁用 2FA，您对此日访问 GitHub.com 的权限将受到限制，直到您重新启用 2FA。此电子邮件以及 GitHub.com 上的一个可关闭横幅将是关于此更改的唯一通知。有关此计划的更多信息，请参阅（[我们的文档][2]）。使软件供应链更加安全是一项团队努力，没有您我们无法做到。您注册 2FA 是保障全球软件安全的重要一步。要查看您帐户的此项及其他安全事件，请访问您的帐户（[安全审计日志][3]）。如果您遇到问题，请通过访问 GitHub（[支持页面][4]）联系支持。谢谢， GitHub 团队

查看原文

Hey birdie-github!We're reaching out to let you know that as announced last year, we will officially ([begin][1]) requiring two-factor authentication (2FA) for certain contributors on GitHub.com. You are receiving this notification because your account meets the criteria for the current enrollment group, and you have 2FA enabled already.You don't need to do anything in response to this email. After September 2nd, 2026 at 00:00 (UTC), you will no longer be able to disable 2FA. If you disable 2FA before then, your access to GitHub.com will be restricted on this date until you re-enable 2FA. This email, and a dismissible banner on GitHub.com, will be the only notifications about this change.For more information about this program, please take a look at ([our documentation][2]).Making the software supply chain more secure is a team effort, and we couldn't do it without you. Your enrollment in 2FA is an impactful step in keeping the world's software secure.To see this and other security events for your account, visit your account ([security audit log][3]).If you run into problems, please contact support by visiting the GitHub ([support page][4]).Thanks, The GitHub Team[1]: https://github.blog/2023-03-09-raising-the-bar-for-software-security-github-2fa-begins-march-13 [2]: https://docs.github.com/authentication/securing-your-account-with-two-factor-authentication-2fa [3]: https://github.com/settings/security-log [4]: https://github.com/contact

GitHub 的双重身份验证将于 2026 年 9 月 2 日强制执行。