Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
Derek Atkins wrote: > > In general, firewalls only get in the way and reduce productivity. > There are a _few_ cases where a minimal packet filter is useful. In any situation where a host is exposed to uncontrollable incoming traffic, a packet filter is an absolute requirement. In many situations where a host is moved from network to network, a packet filter is a damn good idea. (Laptops, for instance.) In fact, in most situations, a packet filter is useful and, indeed, essential to being a good net-neighbor. However, the vast majority of corporate hosts are already in a network where traffic is presumed to be controlled, and thus do not need the hassle of maintaining a packet filter. Note the difference: number of machines, vs number of situations. In most scenarios, packet filters are good; most machines are in one of the few scenarios that don't make packet filters worthwhile. -dsr-
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |