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

Http2 v3 #4772

Closed
wants to merge 17 commits into from
Closed

Http2 v3 #4772

wants to merge 17 commits into from

Conversation

catenacyber
Copy link
Contributor

Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/1947

DRAFT for discussion
Not to be merged

Describe changes:

  • Adds basic HTTP2 parser

Much more work to be done :

  • Commit squashing
  • handle transactions with progress completion
  • parse interesting frame types
  • connection upgrade from HTTP1
  • rules file for applayer events
  • tests
  • robustness against evasions

Modifies #4736 with

  • rebasing
  • parsing/logging/detecting RSTSTREAM PRIORITY WINDOWUPDATE SETTINGS
  • using nom::Err::Incomplete value for `AppLayerResult::incomplete
  • using panic
  • managing to translate a Rust string to uppercase for case-insensitive signatures about enumerations
  • Implementing generic DetectU8Data
  • Right keywords testing framework

@catenacyber catenacyber requested review from jasonish, victorjulien and a team as code owners April 3, 2020 09:42
@catenacyber
Copy link
Contributor Author

Forgot to make it a draft PR again :-(

return -1;
}
strncpy(str_first, str, space - str);
//TODO better no copy, and pass a length argument next ?
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Any thoughts here ? Using Rust to parse signatures ?

@catenacyber catenacyber mentioned this pull request Apr 3, 2020
@catenacyber catenacyber closed this Apr 3, 2020
@catenacyber catenacyber deleted the http2-v3 branch September 4, 2020 08:47
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 19, 2025
To some EVE fields and a "suricata" object that contains an array of
keywords. These are the keywords that map directly to this field, or
somehow cover this field.

This is an attempt at tooling to help with EVE and keyword parity.

Related to tickets: OISF#5642, OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 19, 2025
Currently this script has two commands: "missing" and "having".

"missing" will show eve fields that do not map to any keywords.

"having" will sohw eve fields along with their keyword mappsings,
while also validating that those keywords really exist.

Related to tickets: OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 20, 2025
To some EVE fields and a "suricata" object that contains an array of
keywords. These are the keywords that map directly to this field, or
somehow cover this field.

This is an attempt at tooling to help with EVE and keyword parity.

Related to tickets: OISF#5642, OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 20, 2025
Currently this script has two commands: "missing" and "having".

"missing" will show eve fields that do not map to any keywords.

"having" will sohw eve fields along with their keyword mappsings,
while also validating that those keywords really exist.

Related to tickets: OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 20, 2025
To some EVE fields and a "suricata" object that contains an array of
keywords. These are the keywords that map directly to this field, or
somehow cover this field.

This is an attempt at tooling to help with EVE and keyword parity.

Related to tickets: OISF#5642, OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 20, 2025
Currently this script has two commands: "missing" and "having".

"missing" will show eve fields that do not map to any keywords.

"having" will sohw eve fields along with their keyword mappsings,
while also validating that those keywords really exist.

Related to tickets: OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 20, 2025
To some EVE fields and a "suricata" object that contains an array of
keywords. These are the keywords that map directly to this field, or
somehow cover this field.

This is an attempt at tooling to help with EVE and keyword parity.

Related to tickets: OISF#5642, OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 20, 2025
Currently this script has two commands: "missing" and "having".

"missing" will show eve fields that do not map to any keywords.

"having" will sohw eve fields along with their keyword mappsings,
while also validating that those keywords really exist.

Related to tickets: OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 21, 2025
Currently this script has two commands: "missing" and "having".

"missing" will show eve fields that do not map to any keywords.

"having" will sohw eve fields along with their keyword mappsings,
while also validating that those keywords really exist.

Related to tickets: OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 21, 2025
To some EVE fields and a "suricata" object that contains an array of
keywords. These are the keywords that map directly to this field, or
somehow cover this field.

This is an attempt at tooling to help with EVE and keyword parity.

Related to tickets: OISF#5642, OISF#6463, OISF#4772
jasonish added a commit to jasonish/suricata that referenced this pull request Feb 21, 2025
Currently this script has two commands: "missing" and "having".

"missing" will show eve fields that do not map to any keywords.

"having" will sohw eve fields along with their keyword mappsings,
while also validating that those keywords really exist.

Related to tickets: OISF#6463, OISF#4772
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.

1 participant