Update advanced disclosure email communication methods#4630
Closed
lum1n0us wants to merge 1 commit intobytecodealliance:mainfrom
Closed
Update advanced disclosure email communication methods#4630lum1n0us wants to merge 1 commit intobytecodealliance:mainfrom
lum1n0us wants to merge 1 commit intobytecodealliance:mainfrom
Conversation
lum1n0us
requested review from
TianlongLiang,
loganek,
no1wudi,
wenyongh,
xujuntwt95329 and
yamt
as code owners
yamt
reviewed
Sep 16, 2025
| - 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 sec-announce@bytecodealliance.org 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 sec-announce@bytecodealliance.org about the upcoming security release. It can be accomplished by posting on https://groups.google.com/a/bytecodealliance.org/g/sec-announce. Other ways are also available to communicate the disclosure date. |
Contributor
There was a problem hiding this comment.
are you just suggesting an alternative way to post to the ML?
or is it recommended to use the web interface?
Contributor
Author
There was a problem hiding this comment.
it is recommended to use the web interface
Contributor
There was a problem hiding this comment.
why?
anyway, in that case, it's better to make it clear i guess.
eg. We recommend to use the web interface on ....
Contributor
Author
There was a problem hiding this comment.
It is a kind of BA requests ...
Contributor
There was a problem hiding this comment.
It is a kind of BA requests ...
BA requested to use the web interface instead of emails?
why?
Contributor
Author
There was a problem hiding this comment.
Yes, you are right. Email is sufficient; posting is not mandatory. Confirmed with BA TSC.
lum1n0us
force-pushed
the
fix/sec_runbook_p1
branch
from
f0103c6 to
0af42db
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.