run "lsof -i -P" and you will see what process(es) is/are bound to the open port(s).
On 24 Jul 2002, Crawford Rainwater wrote: > Folks, > > 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. > > Open for some $0.02. > > --- Crawford > > > The I.T.E.C. Company > P.M.B. 146 > 368 South McCaslin Boulevard > Louisville, CO 80027 USA > (303) 604-2550 (voice) > (866) 604-2550 (toll free) > (303) 664-0036 (fax) > http://www.itec-co.com > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > [-] Steve Mickeler [ [EMAIL PROTECTED] ] [|] Todays root password is brought to you by /dev/random [+] 1024D/ACB58D4F = 0227 164B D680 9E13 9168 AE28 843F 57D7 ACB5 8D4F -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
