Re: Portsentry issue/problem
On Wed, 24 Jul 2002 at 22:47:32 +0000, Crawford Rainwater wrote:
> I was experimenting with Portsentry for the first time in a while,
> using nmap to help scan for the open ports on a beta test box (Debian
> 3.0 upgraded).
> What I noticed beforehand, ports were closed beyond 1024 (did
> nmap -sU -sT <IP addy>). After installing Portsentry, there were
> about 10-20 ports open beyond that, including the bo2k and Trinod
> cracker ports.
> I removed Portsentry, ran nmap again, ports are closed. Is this a
> known issue with Portsentry? I have not yet reference the Portsentry
> site at this point, but figured that this may be a common occurance.
Yes, that's the way portsentry works. It listens on some ports to detect
illegal connections to them.
Tomasz Papszun SysAdm @ TP S.A. Lodz, Poland | And it's only
firstname.lastname@example.org http://www.lodz.tpsa.pl/ | ones and zeros.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org