Safety is one of the core principles of Rust, and to that end, we would like to ensure that Rust has a secure implementation. Thank you for taking the time to responsibly disclose any issues you find.
+All security bugs in the Rust distribution should be reported by email to { -security-at-rust-lang-org-anchor }. This list is delivered to a small security team. Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report.
+This email address receives a large amount of spam, so be sure to use a descriptive subject line to avoid having your report be missed. After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement. As recommended by RFPolicy, these updates will be sent at least every five days. In reality, this is more likely to be every 24-48 hours.
+If you have not received a reply to your email within 48 hours, or have not heard from the security team for the past five days, there are a few steps you can take (in order):
+Please note that the discussion forums are public areas. When escalating in these venues, please do not discuss your issue. Simply say that you’re trying to get a hold of someone from the security team.
+ +security-scope-heading = Scope +security-scope--2025-04 = +The Rust Security Response WG handles vulnerability reports for everything maintained and published by the Rust Project:
+rust-langrust-lang-cirust-lang-nurseryrust-analyzerrust-lang.rust-lang.The following things are outside our scope:
+When reporting vulnerabilities, keep in mind that:
+regex crate provides guarantees about untrusted patterns. We consider denial of service with untrusted patterns a security vulnerability only if the time spent inside of the regex crate is not linear, and none of the limit methods in RegexBuilder are able to prevent the attack.If you have doubts on whether something falls within our scope, please reach out and we will provide guidance.
+ security-disclosure-heading = 信息披露政策 security-disclosure-description =Rust 项目有 5 步披露流程：
From 0902886bcabd590f94014c31c4e2ba966ec7f511 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E7=94=9F=E6=9D=82=E7=89=A9=E6=88=BF?= <88823709+TC999@users.noreply.github.com> Date: Wed, 5 Nov 2025 15:00:33 +0800 Subject: [PATCH 2/8] =?UTF-8?q?=E7=AE=80=E4=B8=AD=EF=BC=9A=E5=AE=89?= =?UTF-8?q?=E5=85=A8=E6=94=BF=E7=AD=96?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- locales/zh-CN/security.ftl | 73 +++++++++++++++++++------------------- 1 file changed, 37 insertions(+), 36 deletions(-) diff --git a/locales/zh-CN/security.ftl b/locales/zh-CN/security.ftl index 79c00a38..d949740a 100644 --- a/locales/zh-CN/security.ftl +++ b/locales/zh-CN/security.ftl @@ -5,28 +5,28 @@ policies-security-page-title = 安全政策 security-reporting-heading = 报告漏洞 security-reporting-link = 给 { ENGLISH("security@rust-lang.org") } 发邮件 security-reporting-description--2025-07 = -Safety is one of the core principles of Rust, and to that end, we would like to ensure that Rust has a secure implementation. Thank you for taking the time to responsibly disclose any issues you find.
-All security bugs in the Rust distribution should be reported by email to { -security-at-rust-lang-org-anchor }. This list is delivered to a small security team. Your email will be acknowledged within 24 hours, and you’ll receive a more detailed response to your email within 48 hours indicating the next steps in handling your report.
-This email address receives a large amount of spam, so be sure to use a descriptive subject line to avoid having your report be missed. After the initial reply to your report, the security team will endeavor to keep you informed of the progress being made towards a fix and full announcement. As recommended by RFPolicy, these updates will be sent at least every five days. In reality, this is more likely to be every 24-48 hours.
-If you have not received a reply to your email within 48 hours, or have not heard from the security team for the past five days, there are a few steps you can take (in order):
+安全性是 Rust 的核心原则之一，为此，我们希望确保 Rust 的实现是安全的。感谢您花时间负责任地披露您发现的任何问题。
+Rust 发行版中的所有安全漏洞都应通过电子邮件报告至 { -security-at-rust-lang-org-anchor }。此邮件列表会发送给一个小型安全团队。您的邮件将在 24 小时内收到确认回复，并在 48 小时内收到更详细的回复，说明处理您的报告的下一步措施。
+由于此电子邮件地址会收到大量垃圾邮件，请务必使用描述性主题行，以免您的报告被遗漏。在对您的报告进行初步回复后，安全团队将努力让您了解修复和完整公告的进展情况。根据 RFPolicy 的建议，这些更新至少每五天发送一次。实际上，这更可能是每 24-48 小时一次。
+如果您在 48 小时内未收到电子邮件回复，或者在过去五天内未收到安全团队的消息，您可以采取以下步骤（按顺序）：
Please note that the discussion forums are public areas. When escalating in these venues, please do not discuss your issue. Simply say that you’re trying to get a hold of someone from the security team.
+请注意，讨论论坛是公共区域。在这些场所升级时，请勿讨论您的问题。只需说明您正在尝试联系安全团队的某人即可。
-security-scope-heading = Scope +security-scope-heading = 范围 security-scope--2025-04 = -The Rust Security Response WG handles vulnerability reports for everything maintained and published by the Rust Project:
+Rust 安全响应工作组处理 Rust 项目维护和发布的所有内容的漏洞报告：
rust-langrust-lang-cirust-lang.rust-lang.rust-lang 发布的所有扩展。rust-lang 发布的所有扩展。The following things are outside our scope:
+以下内容不在我们的范围内：
When reporting vulnerabilities, keep in mind that:
+报告漏洞时，请记住：
regex crate provides guarantees about untrusted patterns. We consider denial of service with untrusted patterns a security vulnerability only if the time spent inside of the regex crate is not linear, and none of the limit methods in RegexBuilder are able to prevent the attack.regex crate 对不受信任的模式提供保证。我们仅在 regex crate 内的时间不是线性时，且 RegexBuilder 中的限制方法均无法防止攻击时，才将使用不受信任模式导致的拒绝服务视为安全漏洞。If you have doubts on whether something falls within our scope, please reach out and we will provide guidance.
+如果您对某些内容是否属于我们的范围有疑问，请联系我们，我们将提供指导。
security-disclosure-heading = 信息披露政策 -security-disclosure-description = -Rust 项目有 5 步披露流程：
-Rust 项目有 5 步披露流程：
+此过程可能需要一些时间，尤其是在需要与其他项目的维护人员进行协调时。我们将尽一切努力及时处理错误。但是，我们必须遵循上述发布流程，确保能够以一致的方式处理披露。
security-receiving-heading = 接收安全更新 -security-receiving-description = -接收所有安全公告的最佳方式是订阅 Rust 安全公告邮件列表（或发送电子邮件至 { -rustlang-security-announcements-subscribe-anchor }）。邮件列表的业务量很少，在封禁期过后它会马上收到公共通知。
-我们会在封禁期解除前的 72 小时内向 { -distros-openwall-email-anchor } 公布漏洞，以便于 Linux 发行版更新其软件包。
+security-receiving-description--2025-07 = +接收所有安全公告的最佳方式是订阅 Rust 安全公告邮件列表（或发送电子邮件至 { -rustlang-security-announcements-subscribe-anchor }）。邮件列表的业务量很少，在封禁期过后它会马上收到公共通知。邮件列表上的公告由 Rust 的安全密钥 签名。
+Rust 项目仅为最新的稳定版本以及 beta 和 nightly 渠道 的最新版本提供支持和安全更新。由于 Rust 版本必须在公开环境中构建，我们将在封禁期解除后立即开始发布流程，并在更新的二进制文件可供下载后发布博客文章。
+当漏洞影响软件发行版时，我们将在封禁期解除前 72 小时向 { -distros-openwall-email-anchor } 宣布漏洞，以便发行版在封禁期解除时更新其软件包。
security-pgp-key-heading = 明文 PGP 公钥 From b283c80fcc15f555a281cb055030d856f324fd57 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E7=94=9F=E6=9D=82=E7=89=A9=E6=88=BF?= <88823709+TC999@users.noreply.github.com> Date: Wed, 5 Nov 2025 15:08:35 +0800 Subject: [PATCH 3/8] =?UTF-8?q?=E6=9D=82=E9=A1=B9?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- locales/zh-CN/governance.ftl | 9 +++++++++ locales/zh-CN/teams.ftl | 6 ++++++ 2 files changed, 15 insertions(+) diff --git a/locales/zh-CN/governance.ftl b/locales/zh-CN/governance.ftl index ea28edbf..29edcae7 100644 --- a/locales/zh-CN/governance.ftl +++ b/locales/zh-CN/governance.ftl @@ -13,6 +13,15 @@ governance-rfc-blurb = governance-teams-header = 团队 governance-wgs-header = 工作组 +governance-rust-project-link = 显示所有 Rust 团队成员 + +governance-archived-teams-header = 已归档团队 +governance-archived-teams-description = 一些过去的团队已不再活跃。我们称之为“已归档团队”。 +governance-archived-teams-link = 显示已归档团队 +governance-archived-teams-title = 已归档团队 +governance-archived-alumni-thanks = 我们想感谢所有过去的成员，他们的贡献是无价的！ +governance-archived-teams-intro = 此页面包含已归档的团队，这些团队不再活跃。 + ## governance/index-team.hbs governance-members = 成员和联系方式 diff --git a/locales/zh-CN/teams.ftl b/locales/zh-CN/teams.ftl index 86acce7f..c3ec04a1 100644 --- a/locales/zh-CN/teams.ftl +++ b/locales/zh-CN/teams.ftl @@ -118,3 +118,9 @@ governance-team-wg-rls-2-name = RLS 2.0 工作组 governance-team-wg-rls-2-description = 尝试为 IDE 定制新的编译器体系架构。 governance-team-wg-polonius-name = Polonius 工作组 governance-team-wg-polonius-description = 实现全新借用检查器这个实验性工作 + +governance-team-launching-pad-name = 启动平台 +governance-team-launching-pad-description = 团队的临时家园 + +governance-team-leadership-council-name = 领导委员会 +governance-team-leadership-council-description = 负责整个 Rust 项目的成功，由顶级团队的代表组成 \ No newline at end of file From 3a55ddc70509d3169e9711accf4d39ee42dfc984 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E7=94=9F=E6=9D=82=E7=89=A9=E6=88=BF?= <88823709+TC999@users.noreply.github.com> Date: Sun, 9 Nov 2025 23:24:06 +0800 Subject: [PATCH 4/8] Update locales/zh-CN/security.ftl MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> --- locales/zh-CN/security.ftl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locales/zh-CN/security.ftl b/locales/zh-CN/security.ftl index d949740a..806e6338 100644 --- a/locales/zh-CN/security.ftl +++ b/locales/zh-CN/security.ftl @@ -55,7 +55,7 @@ security-scope--2025-04 =报告漏洞时，请记住：
regex crate 对不受信任的模式提供保证。我们仅在 regex crate 内的时间不是线性时，且 RegexBuilder 中的限制方法均无法防止攻击时，才将使用不受信任模式导致的拒绝服务视为安全漏洞。此过程可能需要一些时间，尤其是在需要与其他项目的维护人员进行协调时。我们将尽一切努力及时处理错误。但是，我们必须遵循上述发布流程，确保能够以一致的方式处理披露。
security-receiving-heading = 接收安全更新 From 6f3fb82fbd1dfb964dd569a0fa5f9ad66227eb92 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E7=94=9F=E6=9D=82=E7=89=A9=E6=88=BF?= <88823709+TC999@users.noreply.github.com> Date: Sun, 9 Nov 2025 23:26:57 +0800 Subject: [PATCH 6/8] Update locales/zh-CN/teams.ftl MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> --- locales/zh-CN/teams.ftl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locales/zh-CN/teams.ftl b/locales/zh-CN/teams.ftl index c3ec04a1..f5a54816 100644 --- a/locales/zh-CN/teams.ftl +++ b/locales/zh-CN/teams.ftl @@ -122,5 +122,5 @@ governance-team-wg-polonius-description = 实现全新借用检查器这个实 governance-team-launching-pad-name = 启动平台 governance-team-launching-pad-description = 团队的临时家园 -governance-team-leadership-council-name = 领导委员会 +governance-team-leadership-council-name = 领导议会 governance-team-leadership-council-description = 负责整个 Rust 项目的成功，由顶级团队的代表组成 \ No newline at end of file From f72d53836fa2077a3c6270cf5b8ef41510ebaa6d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E7=94=9F=E6=9D=82=E7=89=A9=E6=88=BF?= <88823709+TC999@users.noreply.github.com> Date: Sun, 9 Nov 2025 23:27:16 +0800 Subject: [PATCH 7/8] Update locales/zh-CN/security.ftl MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> --- locales/zh-CN/security.ftl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locales/zh-CN/security.ftl b/locales/zh-CN/security.ftl index 64d387b0..da66d697 100644 --- a/locales/zh-CN/security.ftl +++ b/locales/zh-CN/security.ftl @@ -68,7 +68,7 @@ security-disclosure-description--2025-07 =此过程可能需要一些时间，尤其是在需要与其他项目的维护人员进行协调时。我们将尽一切努力及时处理错误。但是，我们必须遵循上述发布流程，确保能够以一致的方式处理披露。
From 031a4827c5ddac8dc283a24b37c496cb4f5745e6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=99=88=E7=94=9F=E6=9D=82=E7=89=A9=E6=88=BF?= <88823709+TC999@users.noreply.github.com> Date: Sun, 9 Nov 2025 23:27:27 +0800 Subject: [PATCH 8/8] Update locales/zh-CN/teams.ftl MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: 许杰友 Jieyou Xu (Joe) <39484203+jieyouxu@users.noreply.github.com> --- locales/zh-CN/teams.ftl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/locales/zh-CN/teams.ftl b/locales/zh-CN/teams.ftl index f5a54816..14bf1f69 100644 --- a/locales/zh-CN/teams.ftl +++ b/locales/zh-CN/teams.ftl @@ -119,7 +119,7 @@ governance-team-wg-rls-2-description = 尝试为 IDE 定制新的编译器体系 governance-team-wg-polonius-name = Polonius 工作组 governance-team-wg-polonius-description = 实现全新借用检查器这个实验性工作 -governance-team-launching-pad-name = 启动平台 +governance-team-launching-pad-name = Launching pad governance-team-launching-pad-description = 团队的临时家园 governance-team-leadership-council-name = 领导议会