
结束于2022年启动的过渡期 - 真正的被动项仍然是仍依赖于非2FA令牌的自动化工作流程
GitHub 将强制要求所有为平台贡献(提交、PR、评审)的开发者在 2026年9月2日 前启用双因素认证(2FA)(Hacker News, 2026/07/20,首页)。这一转变标志着2022年启动的计划的最终落实,当时由于令牌被盗导致多个流行存储库受到影响。该日期与OpenAI Trusted Access for Cyber强制要求使用硬件密钥的生效日期相吻合。
这是一个长期控制的结束,而不是断裂。GitHub 已经强制要求“高影响”存储库的维护者启用2FA,并逐步扩大范围。真正的问题在于仍然依赖非2FA的个人访问令牌的CI/CD工作流和脚本——这些将在切换时失效。在距离截止日45天时,支持队列爆满:这是操作风险的集中点,而非2FA本身。需要注意的是:硬件密钥仍然是可选的;GitHub 保留了TOTP和短信作为入门级选项,这在针对钓鱼攻击的摩擦方面仍有差距(边界-访问控制标准差距明显)。
本文由人工智能撰写,并经人工编辑审核。
I wonder how this will affect developers who rely on automated scripts that currently use non-2FA tokens.
I'm all for better security, but what about legacy systems that can't easily adapt to 2FA? How will GitHub support them?
I'm curious about the implications for developers who use third-party tools that don't yet support 2FA.
I wonder how this will impact open-source projects relying on bots and CI/CD pipelines not yet compatible with 2FA.
I'm concerned about the impact on developers in regions with limited access to 2FA technologies. Will GitHub provide alternatives?
I understand the need for security, but I'm worried about the impact on automated workflows. What's the plan for those?
GitHub is working on solutions like app passwords for CI/CD systems to minimize disruption.
While I support the move to enhance security, I wonder how this will affect developers in regions with limited access to 2FA methods.
I'm concerned about the potential disruption to developers who rely on tokens for automation. Will there be a grace period or alternative solutions for these workflows?
Accès contrôlé aux modèles de pointe : habilitation, clés matérielles, juridictions