Skip to content

Commit

Permalink
docs/SECURITY-PROCESS.md: updates
Browse files Browse the repository at this point in the history
- allow Low+Medium issues to be managed through plain PRs
- update the bug-bounty part to reflect current reality

Closes #10719
  • Loading branch information
bagder committed Mar 10, 2023
1 parent 37a3c63 commit 56f306a
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions docs/SECURITY-PROCESS.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,10 +63,14 @@ announcement.
- Update the "security advisory" with the CVE number.

- The security team commits the fix in a private branch. The commit message
should ideally contain the CVE number.

- The security team also decides on and delivers a monetary reward to the
reporter as per the bug-bounty policies.
should ideally contain the CVE number. If the severity level of the issue is
set to Low or Medium, the fix is allowed to get merged into the master
repository via a normal PR - but without mentioning it being a security
vulnerability.

- The monetary reward part of the bug-bounty is managed by the Internet Bug
Bounty team and the reporter is asked to request the reward from them after
the issue has been completely handled and published by curl.

- No more than 10 days before release, inform
[distros@openwall](https://oss-security.openwall.org/wiki/mailing-lists/distros)
Expand Down

0 comments on commit 56f306a

Please sign in to comment.