Page MenuHomeFreeBSD

Make 502.pfdenied find blacklistd/* filter names dynamically
ClosedPublic

Authored by lidl on Sep 29 2016, 8:52 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Apr 8, 10:10 PM
Unknown Object (File)
Tue, Mar 19, 2:04 AM
Unknown Object (File)
Feb 15 2024, 2:53 PM
Unknown Object (File)
Dec 23 2023, 4:01 AM
Unknown Object (File)
Oct 27 2023, 1:12 AM
Unknown Object (File)
Sep 10 2023, 9:46 AM
Unknown Object (File)
Aug 26 2023, 9:30 PM
Unknown Object (File)
Jun 18 2023, 3:14 PM
Subscribers

Details

Reviewers
emaste
kp
Summary

This change is needed to make the 520.pfdenied script find the new blacklistd/* anchor
points for reporting blocked traffic.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 5451
Build 5661: CI src buildJenkins

Event Timeline

lidl retitled this revision from to Make 502.pfdenied find blacklistd/* filter names dynamically.
lidl updated this object.
lidl edited the test plan for this revision. (Show Details)
lidl added a reviewer: emaste.
lidl set the repository for this revision to rS FreeBSD src repository - subversion.
etc/periodic/security/520.pfdenied
47
# echo $(pfctl -a "blacklistd" -sA)
pfctl: DIOCGETRULESETS: No such file or directory

So if there are no blacklistd anchors we end up with errors in the log, right?

lidl added inline comments.
etc/periodic/security/520.pfdenied
47

Good catch. I will upload a new diff momentarily.

lidl marked an inline comment as done.

Address review comment about error messages when the pf anchor isn't defined.

kp edited edge metadata.
This revision is now accepted and ready to land.Oct 4 2016, 9:06 PM

I forgot to put the Phabricator review URL in the commit message. Manually closing.