-
Notifications
You must be signed in to change notification settings - Fork 3.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
snort3: bump to 3.5.1.0 #25267
base: master
Are you sure you want to change the base?
snort3: bump to 3.5.1.0 #25267
Conversation
Bump libdaq3 to 3.0.17 as this new version is required by snort3 latest versions. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
@Neustradamus Since i see you love doing research I'm curious how much people are using downstream patch (and maybe mine) for PCRE2 in package repositories |
Had to make two modifications as detailed here. After that, snort seems to be functional. Recommend merge. Build system: x86/64 |
Honestly using pcre2_to_regex doesn't make sense and the compile error should be investigated... Would be good to have repro steps... |
@Ansuel - I PM'ed a few of the active snort users in the forums asking them to join the conversation (xxxx and efahl)
To save time looking up that thread, these are the two changes I made to get this working:
|
It still seems more appropriate to add wrappers in the API code so that the exported symbol names don't change (and thus the user defined lua-config files would need no modifications). The changes in an underlying library should not propagate into breaking changes in the config files (even if the original implementers of snort made the poor choice of using the underlying library's name in their public API). |
@efahl this might be O.K. for trivial library/program, not for a security intrusion program where something silently changing might produce intrusion not detected. I feel manual checkup is still needed. But yes needs to se... all the rename from pcre to pcre2 can be skipped but we need to discuss that. |
Upstream is actively working on this and thinking about the user experience (not changing configure files or tweaking rules). I do not know timing thought and since our snort package has not been updated since dropping pcre going back 5 months now, my recommendation is to merge this even though doing so will require users to make a few tweaks. |
Bump snort3 to 3.5.1.0. Manually refresh the PCRE2 patch to latest changes. Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
3.5.1.0 works fine for me Build system: x86/64 |
@Ansuel - can you update for 3.5.2.0?
|
Bump snort3 to 3.5.1.0. Manually refresh the PCRE2 patch to latest
changes.
Signed-off-by: Christian Marangi ansuelsmth@gmail.com