suricata-7.0.2_4 - Use pfctl_table_add_addrs() and fix memory leaks and compiler warnings. #1325
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This request was manually merged by kprovost, so closing it manually since GitHub will not auto close it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
suricata-7.0.2_4
This update to the Suricata custom blocking plugin used for Legacy Blocking Mode on pfSense includes some general code cleanup in the form of formatting fixes and other cosmetic issues. It also fixes two memory leaks and replaces a legacy ioctl() call with the corresponding pfctl_table_add_addrs() function from the new libpfctl wrapper library for pfctl functionality.