Skip to content

Commit

Permalink
Github security reporting: Use new Github vulnerability mechanism
Browse files Browse the repository at this point in the history
* New Github vulnerability reporting mechanism was enabled for this repo.
* Update description to use this mechanism (instead of using emails).
  This simplifies how to keep track of the state of this security issue.
  • Loading branch information
jenisys committed Nov 14, 2022
1 parent c3cfd40 commit 97ddb2b
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions .github/SECURITY.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,11 @@ HINT: Older versions are not supported.

## Reporting a Vulnerability

SHORT VERSION: Please report security issues by emailing to [behave-security@noreply.github.com](mailto:jenisys@users.noreply.github.com) .
Please report security issues by using the new
[Github vulnerability reporting mechanism](https://github.com/behave/behave/security/advisories)
that is enabled for this repository.

If you believe you’ve found something in Django which has security implications,
please send a description of the issue via email to the email address mentioned above (see: SHORT VERSION).
Mail sent to that address reaches the security team.

Once you’ve submitted an issue via email, you should receive an acknowledgment from a member of the security team within 48 hours,
and depending on the action to be taken, you may receive further followup emails.
SEE ALSO:

* https://github.com/behave/behave/security/advisories
* https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing/privately-reporting-a-security-vulnerability

0 comments on commit 97ddb2b

Please sign in to comment.