"[EMAIL PROTECTED]" <[EMAIL PROTECTED]>: > We hereby reject this utter horseshit unreservedly.
Agreed - when it's intended to "protect" aunt Annie's Xmas present. It just makes NO SENSE to have PC's listening on lots of ports, by default on any interface, and then add a PFW to prevent anyone from accessing them. (much like building a wall in front of your house because your doors and Windows(TM) have broken locks). In particular because most Annie's have no clue what IP is, and undesired egress traffic easily bypasses PFW's (if the malware hasn't shut down the darn thing right away). Classic PFW = Snake Oil: http://www.samspade.org/d/firewalls.html If Annie's weren't members of Administrators, and members of Administrators would not have access to apps like IE and OE, and WindowsUpdate would not require admin privs to download, and there wouldn't be so many privesc sploitz, and the FS and registry would have much tighter perms by default, PFW's *would* make sense - for blocking undesired egress traffic. That is, provided that the PFW reliably starts before net I/O is possible, runs in "Safe Mode With Networking", and is not crowded with bugs itself. Cheers, Erik _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
