-
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
Applayer plugin 5053 v3.21 #12383
Applayer plugin 5053 v3.21 #12383
Conversation
Because some alprotos will remain static and defined as a constant, such as ALPROTO_UNKNOWN=0, or ALPROTO_FAILED. The regular already used protocols keep for now their static identifier such as ALPROTO_SNMP, but this could be made more dynamic in a later commit. ALPROTO_FAILED was used in comparison and these needed to change to use either ALPROTO_MAX or use standard function AppProtoIsValid
Ticket: 5053 The names are now dynamically registered at runtime. The AppProto alproto enum identifiers are still static for now. This is the final step before app-layer plugins.
Ticket: 5053
It needs app-layer registration for the names
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #12383 +/- ##
==========================================
- Coverage 82.46% 80.63% -1.84%
==========================================
Files 914 915 +1
Lines 258316 258440 +124
==========================================
- Hits 213030 208401 -4629
- Misses 45286 50039 +4753
Flags with carried forward coverage won't be shown. Click here to find out more. |
Requested changes : add commit to add the template as an app-layer plugin |
WARNING:
Pipeline 24186 |
Changed my mind on this. I'll merge this PR now to avoid future rebase cost. But please do the follow up PR with the template soon. |
Merged in #12389, thanks! |
Link to ticket: https://redmine.openinfosecfoundation.org/issues/
https://redmine.openinfosecfoundation.org/issues/5053
Describe changes:
#12372 with
Note that there is still #12307 to fix the limitation of probing parsers against 32 protocols (meaning any new app-layer like one in a plugin may be affected by this bug if it uses probing parsers for protocol detection)
After that, a next step can be to completely remove
ALPROTO_SNMP
from C codeAnd also add template examples cf https://redmine.openinfosecfoundation.org/issues/4102