You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/doc/contrib/src/process/security.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ The general order of events happens as follows:
12
12
1. The WG will start a private Zulip stream to coordinate discussion and plans for a fix.
13
13
1. The WG will pull in one or more team members into the Zulip stream ("responders").
14
14
- Security vulnerabilities are **embargoed** until they are released publicly.
15
-
People who are brought into these discussions should **not** discuss the issue with *anyone* outside of the group, or with your employer, without first consulting The WG.
15
+
People who are brought into these discussions should **not** discuss the issue with *anyone* outside of the group, including your employer, without first consulting The WG.
16
16
1. A discussion then starts to evaluate the severity of the issue and what possible solutions should be considered.
17
17
This includes figuring out who will volunteer to actually develop the patches to resolve the issue, and who will review it.
18
18
1. The WG will create a temporary private fork of the `rust-lang/cargo` repo using GitHub's [repository security advisory][github-advisory] system.
0 commit comments