socketfilterfw failing to add daemon on Big Sur 11.0.1 Beta

When running
/usr/libexec/ApplicationFirewall/socketfilterfw --add <path>
the error message: "The file path you specified is invalid" is returned. This as worked on all the previous macOS versions. Has anyone run into this? Thank you.

Replies

Has a bug been filed for this? This is one of 3 pages on Google for the issue "The file path you specified is invalid" on Big Sur.

This bug persists on MacOS Ventura 13.2.1 on mac mini late 2018 Intel i7 6core.

$ /usr/libexec/ApplicationFirewall/socketfilterfw --listapps
ALF: total number of apps = 5

1 :  /System/Library/CoreServices/RemoteManagement/ARDAgent.app
 	 ( Allow incoming connections )

2 :  /opt/exporter_proxy/exporter_proxy
 	 ( Block incoming connections )

3 :  /opt/node_exporter/node_exporter
 	 ( Allow incoming connections )

4 :  /opt/script_exporter/script_exporter
 	 ( Block incoming connections )

5 :  /System/Library/CoreServices/ControlCenter.app
 	 ( Allow incoming connections )

$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock '/opt/exporter_proxy/exporter_proxy'
The file path you specified does not exist
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --remove "  /opt/exporter_proxy/exporter_proxy"
The file path you specified does not exist
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock "2 :  /opt/exporter_proxy/exporter_proxy"
The file path you specified does not exist
$ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock /opt/exporter_proxy/exporter_proxy
The file path you specified does not exist

See this post.

Without a new bug number it’s impractical for me to check on the state of this issue, or indeed know whether the issue is actually being tracked by the folks working on the firewall.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"