-
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
Dynamic alprotos : make SNMP totally dynamic v8 #12533
base: master
Are you sure you want to change the base?
Conversation
CID 1640392 Would happen only if we reached 15 protocols handling files
Ticket: 5053 Do not asume that we know the number of alprotos at the end of AppLayerNamesSetup, but make arrays allocated by later AppLayerProtoDetectSetup dynamic so that it can be reallocated from AppLayerParserRegisterProtocolParsers This helps have a single entry point for a protocol like SNMP
So that we do not have to know g_alproto_max to register dynamically a new protocol from its name
Ticket: 5053 Move enum OutputJsonLogDirection and struct EveJsonTxLoggerRegistrationData from C to rust
and cast and also remove unneeded mut and rustfmt
Ticket: 5053
#define SC_PLUGIN_API_VERSION 8 | ||
#define SC_PLUGIN_API_VERSION 0x801 |
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.
I still don't think we should be twiddling this for a development release.
For 8.0, we should use something like 800000, or something.. 9.0, 900000. If we did an 8.1 then 800100.
But if we are going to twiddle it, just start at 1.. Then 2, then 3, etc..
Information: QA ran without warnings. Pipeline 24663 |
Link to ticket: https://redmine.openinfosecfoundation.org/issues/
https://redmine.openinfosecfoundation.org/issues/5053
Describe changes:
#12470 with needed rebase