pf rule execution says it listens as root, but it connects as the _unbound user, when configured to run as _unbound. Why doesn't it listen, bind, etc. as root, drop privileges and pledge away privilege escalation? Is it to avoid more #ifdef hell? Or can you not listen to a privileged port if you drop privileges?
- why does unbound listen as root Luke Small
- Re: why does unbound listen as root Gregory Edigarov