Re: How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

Sorry, no go. I found a solution on superuser with 0 votes ;-). https://superuser.com/a/940696/582447 It turns out that I just had to turn the firewall off and on again. It might have been a necessary last step to make it regenerate something, but after that step, a reboot (or just port unload

Re: How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

Just turn off your firewall! 😝 Seriously, the macOS firewall is an Application firewall. If that suits your risk profile, you can control it through the command line: /usr/libexec/ApplicationFirewall/socketfilterfw -h Port- and packet-based filtering is handled by pfctl, and that’s a lot more

Re: How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

It seems to be a code signing issue for /opt/local/sbin/unbound, but I haven’t found out how to get rid of it and MacPorts doesn’t handle it itself (i.e. forces the app to end into a good state or warn why it can’t do it). Gerben Wierda (LinkedIn ) R&A E

How can I make unbound's accepting of incoming network connections in application firewall in Catalina 'stick'?

I am running an extensive MacPorts (with postfix, dovecot, nginx, minion, etc.) on my macOS Server, which is still running macOS Mojave. On one of the other Macs, running macOS Catalina, I run a backup unbound caching nameserver. This also offers me a way to do some minimal testing of the MacPo