Skip to content

Update advanced disclosure email communication methods #4630

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update advanced disclosure email communication methods #4630

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions doc/security_issue_runbook.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ For information on what types of issues are considered security vulnerabilities

- Finalize Details: Once a fix is developed and the vulnerability is fully understood, finalize the advisory details and prepare for public release. Ensure the security issues are resolved in the private fork.
- Request CVE: Use the Big Green Button on the advisory to request a CVE number from GitHub staff.
- Advanced Disclosure Email: Decide on a disclosure date, typically within a week, and send an email to [email protected] about the upcoming security release. Other ways are also available to communicate the disclosure date.
- Advanced Disclosure Email: Decide on a disclosure date, typically within a week, and send an email to [email protected] about the upcoming security release. It is recommended to accomplish this by posting on https://groups.google.com/a/bytecodealliance.org/g/sec-announce. Other ways are also available to communicate the disclosure date.

``` markdown
```markdown
> A template for the advanced disclosure email

The Wamr project would like to announce a forthcoming security release.
Expand All @@ -46,7 +46,7 @@ The highest severity issue fixed in this release is classified as XXX based on t
- Manually Make PRs from Private Fork: Transfer the necessary pull requests from the private fork to the public repository.
- Merge and Trigger Releases: Merge the version bump PRs and trigger the release process.
- Publish GitHub Advisories: Delete the private forks and use the Big Green Button to publish the advisory.
- Send Security Release Email: Send a follow-up email to [email protected] describing the security release. Other communication channels can also be used to inform users about the security release.
- Send Security Release Email: Send a follow-up email to [email protected] describing the security release. It is recommended to accomplish this by posting on https://groups.google.com/a/bytecodealliance.org/g/sec-announce. Other methods are also available to communicate the disclosure date.

```markdown
> A template for the security release email
Expand Down