diff --git a/locales/core.ftl b/locales/core.ftl index 1eca7b1a..50aad87c 100644 --- a/locales/core.ftl +++ b/locales/core.ftl @@ -1,8 +1,6 @@ -security-at-rust-lang-org-anchor = { EMAIL("security@rust-lang.org") } -rust-security-team-key-href = /static/keys/rust-security-team-key.gpg.ascii --rust-pgp-key-mit-keyserver-href = - https://pgp.mit.edu/pks/lookup?op=vindex&search=0xEFB9860AE7520DAC" -wikipedia-rfpolicy-href = https://en.wikipedia.org/wiki/RFPolicy @@ -20,6 +18,8 @@ https://groups.google.com/forum/#!forum/rustlang-security-announcements -rust-security-announcements-mailing-list-href = https://groups.google.com/group/rustlang-security-announcements/subscribe +-rust-security-supported-channels-href = + https://doc.rust-lang.org/book/appendix-07-nightly-rust.html -rustlang-security-announcements-subscribe-anchor = rustlang-security-announcements+subscribe@googlegroups.com -distros-openwall-email-anchor = diff --git a/locales/en-US/security.ftl b/locales/en-US/security.ftl index d5f67bb6..b45caf46 100644 --- a/locales/en-US/security.ftl +++ b/locales/en-US/security.ftl @@ -5,9 +5,9 @@ policies-security-page-title = Security policy security-reporting-heading = Reporting security-reporting-link = email { ENGLISH("security@rust-lang.org") } -security-reporting-description--2022-01 = +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. If you would like, you can encrypt your report using our public key. This key is also On MIT’s keyserver and reproduced below.

+

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):