Re: Port 135
From: \ (dvader@deathstar.mil)Date: 03/19/02
- Next message: FoKa: "What is usualy on 113 port?"
- Previous message: Markus Tröger: "Re: ZoneAlarm 3 + IE 5.5/6 - connects at startup ..."
- In reply to: Tore Lund: "Re: Port 135"
- Next in thread: Sirius: "Re: Port 135"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "\"Crash\" Dummy" <dvader@deathstar.mil> Date: Tue, 19 Mar 2002 12:03:48 -0500
>For my own part I suspect anyone who has a product to sell. Maybe
>pcflank.com or unixcircle.com are more objective and/or have more
>complete tests.
I know the feeling, but I've checked this scan pretty thoroughly. I've
turned my Personal Web Server (PWS) on and off to see what the effect is. I
have also used IPSec in conjunction with the IP Filter and a firewall. I
think the scan is real. I just don't know how it works to get around the
filter. On other scan sites, including the Sygate "Quick scan," everything
shows up as blocked. I haven't tried any of the really thorough scans
because they take several hours to run.
I can block the active ports with IPSec, but I have to use an explicit
filter to do it. I would like to have a rule to block everything not
explicitly permitted.
-- Dave "Crash" Dummy Certified Dilettante Dave@gpick.com http://lists.gpick.com
- Next message: FoKa: "What is usualy on 113 port?"
- Previous message: Markus Tröger: "Re: ZoneAlarm 3 + IE 5.5/6 - connects at startup ..."
- In reply to: Tore Lund: "Re: Port 135"
- Next in thread: Sirius: "Re: Port 135"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|