Alastair Poole wrote:
This problem only occurs on localhost. I don't think it is mere luck,
these are too frequent and strange for this.
I tried the scanning program on localhost. I modified it to wait for the
user to press Enter when it encounters an open port.
On my system I normally have listening TCP ports 25, 631 and 1024.
And yes, the scanning program sometimes finds other open ports.
This is netstat output when it happens:
michich@michichnb:~> LC_ALL=C netstat -ntp | grep scan
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:1774 127.0.0.1:1774 ESTABLISHED 17510/scan
The TCP socket connected to itself. I don't know if it's expected
behaviour. It agree it is strange, because we didn't call listen() on
the socket.
Michal
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
