Re: Closing Open Ports
From: Karl Levinson [x y] mvp (levinson_k_at_despammed.com)
Date: 10/15/03
- Next message: Keith Langmead: "Re: how to remove run from start menu"
- Previous message: Karl Levinson [x y] mvp: "** READ THIS BEFORE POSTING - answers to frequently asked questions 2003.10.15"
- In reply to: j: "Closing Open Ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 15 Oct 2003 07:28:25 -0400
There's no logging, so if you're hacked, you've no idea who did it, and if
there's a problem, you've no idea what port you need to open up. There's no
simple GUI like a firewall management console to easily set up multiple
rules. There's no reporting or alerting or intrusion detection. And
dynamic protocols like FTP don't work well through such rules, unless you
open up a whole lot of ports you didn't really want to open. And, a trojan
or virus could potentially disable IPsec. And IPsec can't tell you which
executable is generating network traffic or block traffic by executable,
like many free personal firewalls can. By comparison, the XP ICF firewall
is arguably way better than IPsec rules in a number of ways.
Bottom line, IPSec is not a good firewall, especially if you're not already
a TCP/IP filtering expert and can troubleshoot setup problems without a log
of blocked packets. You can always get better functionality and more
security by going to a real firewall.
"j" <anonymous@discussions.microsoft.com> wrote in message
news:05f901c392d0$f70c09c0$a401280a@phx.gbl...
> Couldn't you use IPSec IP filter lists to block open ports
> as well?
- Next message: Keith Langmead: "Re: how to remove run from start menu"
- Previous message: Karl Levinson [x y] mvp: "** READ THIS BEFORE POSTING - answers to frequently asked questions 2003.10.15"
- In reply to: j: "Closing Open Ports"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
