You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2023. It is now read-only.
I'd like to strongly suggest that the pf settings be verified for tampering. It is extremely easy (like, by using 17.0.0.0/8 signed software and exporting a variable) to modify it. The socket/application firewall is deprecated (and I believe can be bypassed?) since the introduction of the packet filter.
The text was updated successfully, but these errors were encountered:
geoff-nixon
changed the title
Suggestion: (at least) monitor, in not fortify, packet filter firewall.
Suggestion: if not fortify, monitor changes to packet filter firewall.
Jul 10, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'd like to strongly suggest that the
pf
settings be verified for tampering. It is extremely easy (like, by using 17.0.0.0/8 signed software and exporting a variable) to modify it. The socket/application firewall is deprecated (and I believe can be bypassed?) since the introduction of the packet filter.The text was updated successfully, but these errors were encountered: