-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
dns: add dns.rcode keyword v2 #10097
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good work, Hadiqa!
Are you able to see s-v failures locally too?
yes, so the SV tests for rcode seem to all be failing. |
I see. Do you need help with that? Could you please share if you have an idea why it might be happening? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As Shivani has indicated, could you go over the CI failures and share with us if you have an idea of why are the tests failing?
I've also left a review on the SV PR that may add insights on this.
For this PR, for now, just some nit comments inline.
{ | ||
sigmatch_table[DETECT_AL_DNS_RCODE].name = "dns.rcode"; | ||
sigmatch_table[DETECT_AL_DNS_RCODE].desc = "Match the DNS header rcode flag."; | ||
sigmatch_table[DETECT_AL_DNS_RCODE].url = "/rules/dns-keywords.html#dns-rcode"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: once the code-related changes are done, we'll need to populate the documentation section mentioned in this line ;)
@@ -0,0 +1,23 @@ | |||
/* Copyright (C) 2019 Open Information Security Foundation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: year 2024
@@ -0,0 +1,87 @@ | |||
/* Copyright (C) 2023 Open Information Security Foundation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit year 2024, now :P
I don't really know why the failures are happening. I didn't see any errors when I ran the code locally. I'll create a new PR and see if the continue to happen. |
Can you run the suricata verify tests locally and see what is the output in the eve.json logs? If the checks are failing, comparing what is on the checks with what the logs actually looks like is one of the first things I do, if there are no errors, to debug a failing test. |
New PR: #10126 |
Feature #6621
Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/6621
Previous PR: #10087
Describe changes:
cargo clippy --all-features
command as recommended.SV_BRANCH=OISF/suricata-verify#1567