init: use pledge(2) after suricata initialization. #3742
Closed
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.
Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/2895
Describe changes:
pledge(2)
can be used on OpenBSD to restrict suricata possibleoperation on the system once initialization is completed.
The process promises to only make use of:
stdio
to allowread(2)
on IPS rules andwrite(2)
on log filerpath wpath cpath
to allow log rotation and rule reloadunix
to operate the control unix socket and log unix socketsdns
to retrieve DNS from recvfrom(2)/sento(2) in IPFW modebpf
as suricata uses libpcap, which uses theBIOCGSTATS
operationPRScript output (if applicable): N/A