Linked by Thom Holwerda on Wed 19th Dec 2007 21:46 UTC, submitted by Scott
Permalink for comment 292326
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2007-01-22
Well OSX never had PF as in OpenBSD's pf see link http://www.netbsd.org/docs/network/pf.html . The firewall that was in 10.4 and is still in 10.5 is IPFW from FreeBSD see link http://www.freebsd.org/cgi/man.cgi?query=ipfw&apropos=0&sektion=0&m...
The current thing apple is calling the firewall, is the Apple Application Firewall. This does not work the same way say PF or IPFW would. Rather then work by hooking into the kernel and filtering networking data at a low level; where you can see if the data is tcp or udp, the application firewall is allowing or denying applications ability to talk to the network. I.E. should safari.app be able to send and receive data. Now this is not a bad idea but the issue I have is that the front end program apple made for OS 10.5 is does not let you setup IPFW rules saying block all TCP traffic from IP BLAH. or Deny all IP in and then setup explicit allow rules. Apple IMHO needs to add and advanced firewall editing in the system prefs gizmo for the firewall to allow you to add ipfw rules . The application firewall's default setup does not address a number of firewall issues that ipfw + the application firewall could.