4 ms·
But it's not a misconfiguration, it's a bug as the article explains. And it's not the author's fault that Apple named their firewall the same as OpenBSD.
by thedanbob 3y ago
But it's not a misconfiguration, it's a bug as the article explains. And it's not the author's fault that Apple named their firewall the same as OpenBSD.
- voytec 3y agoIt's not a case of naming something similarily to other software. OSX used FreeBSD's ipfw and around the time they renamed the OS to macOS, they switched to OpenBSD's pf. Now they've screwed up either configuration or implementation but to me - it doesn't read like a bug in pf.
- fullspectrumdev 3y agoIt’s a bug in the program named pf on macOS. It’s not that deep. Nobody is blaming OpenBSD’s pf here.
- Khaine 3y agoI believe Apple used FreeBSD's implementation of pf, as it also has the same syntax. OpenBSD pf has evolved since then and their are minor syntactic differences for some rules between freebsd pf and openbsd pf.