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.

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

security: update policy wrt CVE ID's #10354

Closed
wants to merge 1 commit into from

Conversation

victorjulien
Copy link
Member

To match that we'll now request CVE ID's ourselves as well, and we can do it for reported issues as well.

See also:
https://forum.suricata.io/t/security-new-cve-policy/4473

To match that we'll now request CVE ID's ourselves as well,
and we can do it for reported issues as well.

See also:
https://forum.suricata.io/t/security-new-cve-policy/4473
@victorjulien victorjulien requested a review from a team as a code owner February 10, 2024 09:45
@victorjulien victorjulien requested review from jasonish and catenacyber and removed request for a team February 10, 2024 09:48
Copy link

codecov bot commented Feb 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (7e4dba7) 82.32% compared to head (d11691f) 82.32%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #10354      +/-   ##
==========================================
- Coverage   82.32%   82.32%   -0.01%     
==========================================
  Files         978      978              
  Lines      272147   272147              
==========================================
- Hits       224057   224049       -8     
- Misses      48090    48098       +8     
Flag Coverage Δ
fuzzcorpus 63.59% <ø> (ø)
suricata-verify 61.47% <ø> (-0.03%) ⬇️
unittests 62.83% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@@ -69,7 +75,7 @@ a public release addressing the issue.
We will acknowledge you in the release notes and the release announcement. If you
do not want this, please clearly state this.

We will not request a CVE, but if you do please let us know the CVE ID.
Please let us if you've requested a CVE ID. If you haven't, we can do it.
Copy link
Contributor

Choose a reason for hiding this comment

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

typo let us know ?

@victorjulien
Copy link
Member Author

replaced by #10369

@victorjulien victorjulien deleted the secpol-update/v1 branch February 20, 2024 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants