Skip to content
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

Jump to bottom

CNA scope conflict improvement #6612

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

CNA scope conflict improvement #6612

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4b7bc9f
CNA scope conflict improvement
Kevin-CB Aug 14, 2023
3b19a45
Merge branch 'master' into CNA-scope-conflict
MarkEWaite Apr 26, 2024
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
2 changes: 1 addition & 1 deletion content/security/for-maintainers.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,7 +101,7 @@ The following is a rough approximation of the typical recommended lifecycle of a
.. The security team provides a private repository for that work in the `jenkinsci-cert` GitHub organization.
.. Work usually happens on a branch, and a corresponding pull request will be used for review.
. A *date and time of the release is coordinated* between the security team and maintainers.
The security team handles CVE ID assignment, advance notification of users, and creation of the security advisory.
The security team handles CVE ID assignment (in cases where there is no CNA scope conflict), advance notification of users, and creation of the security advisory.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We still handled it by coordinating with the other CNA, we just didn't assign it ourselves.

Do you prefer an approach like this one ,or do you think it should not be mentioned?

Suggested change
The security team handles CVE ID assignment (in cases where there is no CNA scope conflict), advance notification of users, and creation of the security advisory.
The security team handles CVE ID assignment (assignment may require coordination with another CNA in case of a scope conflict), advance notification of users, and creation of the security advisory.

. The *security fix is merged*.
For details, see link:#merging[Merge the Fix] below.
. A version of the plugin containing the fix is *uploaded to a staging repository* (see link:#upload[Stage with Maven] below).
Expand Down