On Sun, 19 Jun 2005 23:42:04 -0700, Jim Clark
Shouldn’t the OS catch the Apps trying to breach. I mean Skype or any
others. The OS should be take the responsibility to stop the intruders.
Well, it's like the Maginot Line; defences face outwards. The view is
that once a program is running within the system, it's presumably
supposed to be there so everything is done to "help" it.
Consider that many apps, Skype included, require the use of
non-standard ports. When users choose to install these, they expect
them to work; in fact, Windows usually gets blamed if they do not.
Part of the installation process for such apps is to reconfigure the
firewall to be compatible with what they are trying to do - in the
case of Skype, perform Voice over IP (VoIP) phone calls.
This is a erlatively unfamiliar application that Skype aims to make
commonplace, in part by making it easier. Expecting users to dabble
with custom firewall settings does not meet that goal.
Consider also that if the user finds Skype doesn't work unless the
firewall is disabled, they will either not use Skype (bad for Skype,
and the user who hoped to do what Skype can do) or disable the
firewall altogether (disasterous for the user).
Now I've seen the point made that allowing programs running on XP to
change firewall settings is a Bad Thing, and I agree up to a point,
but then again, many malware routinely smite down a long list of
firewalls, av, and other defensive tools. If you had Norton Internet
Security, or Kerio, or Sygate Pro etc. and these were disabled by
resident malware, you'd be just as dead.
On the historical Maginot line, see...
http://www.smithsonianmag.si.edu/smithsonian/issues97/jun97/maginot.html
....and then think about how easy it is to sit in a car with a laptop
and tune into someone else's wireless LAN via their wireless broadband
NAT router. Join the dots from there (hint: admin shares).
-- Risk Management is the clue that asks:
"Why do I keep open buckets of petrol next to all the
ashtrays in the lounge, when I don't even have a car?"