SliTaz Forum
You are not logged in.
Pages: 1
Over the past hour or so I have run pscan a dozen times over the entire port range of localhost ...
pscan localhost -b -p 1 -P 65535
... and more often than not one or two of the higher ports were open. Is there any explanation for this? Does anyone else see this in their Slitaz 3.0 installation? Is pscan buggy? Is there something wrong in Slitaz 3.0? Are Sarkozy's spooks peeking into my computer to find out about the armed communist uprising I'm trying to organize? Questions, questions ...
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
36821 tcp open unknown
60141 tcp open unknown
65531 closed, 4 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
65533 closed, 2 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
41588 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
40349 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
57658 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
65533 closed, 2 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
37025 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
65533 closed, 2 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
35340 tcp open unknown
51811 tcp open unknown
65531 closed, 4 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
60573 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
36619 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Scanning localhost ports 1 to 65535
Port Proto State Service
631 tcp open unknown
6000 tcp open unknown
42621 tcp open unknown
65532 closed, 3 open, 0 timed out (or blocked) ports
Offline
pscan is designed to only scan internally to check open ports. It just doesn't specify for what they're being used and it's also not very accurate beyond 1024. A better way to check is to use the netstat command (preferably netstat -t).
Offline
Thanks for the reply, Trixar. I think, pscan is indeed useless if it produces such wildly inaccurate results on the higher ports. Strangely, pscan takes quite a long time to scan the 64k ports. One would expect a better result from such a procedure. Buggy code? Wrong scanning method? Anyways, I've just checked the ports a couple of times with netstat -t and everything was alright. I also temporarily installed nmap and ran a check ... and again, all the ports were closed (except cups and X11). So, I guess I can go on with my insurrection then? :-)
Offline
Pages: 1
[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]