[prev in list] [next in list] [prev in thread] [next in thread] 

List:       focus-sun
Subject:    Re: Determining unnessary ports
From:       Bennett Todd <bet () RAHUL ! NET>
Date:       2000-06-20 13:50:28
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

2000-06-19-18:13:15 David LaPorte:
> What exactly is the problem with portscanning local machines?
> I've done it nightly without any ill effects...

Sure, there's no ill effects (usually, barring some scanner options
and some weak IP stacks). But given the possibility of packet
filtering restricting the visibility of some open ports, and the
unreliability of port scanning on UDP, listing open ports with a
locally-executed program is way more effective --- not to mention
more informative.

Netstat is a fine fallback, but I really cannot recommend lsof too
highly; it not only tells you exactly what addr:port combos are
being listened on (and whether TCP or UDP), it also tells you the
name the daemon doing the listening, the user it's running as, and
its pid.

- -Bennett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE5T3akL6KAps40sTYRAkcwAJ49hmCo8x8A+8cdWcH1hSaEJ3o6+QCgguXb
TiCAGOyrMRZhV3JfMkNpcJU=
=PQeh
-----END PGP SIGNATURE-----

[prev in list] [next in list] [prev in thread] [next in thread]