Re: ambiguity about nmap results

["sara fink" <sara.fink () gmail com>]

I tried lsof -i now. Yes, it is very good. Useful to know the program
attached to port iinstead of checking a web site what protocol is
responsible for a certain port.

On Sat, May 31, 2008 at 3:13 AM,  <doug () hcsw org> wrote:
> FWIW:
>
> -bash-3.2$ uname -a
> OpenBSD blackhole 4.3 GENERIC#698 i386
> -bash-3.2$ pwd
> /usr/ports/net/nmap
> -bash-3.2$ grep ^V= Makefile
> V=              4.53
>
> Also, several people suggested "netstat -a" for looking for open
> ports on your local machine. netstat is OK but even better IMO is
> "lsof -i" (may need root or kmem privs). It will give you much more
> info such as which process owns the socket, what the file descriptor
> is in that process, etc. And when you're developing, "lsof -p PID"
> is invaluable. It will tell you all sockets, files, mmaps, dynamic
> libraries loaded etc. Once you go lsof you never go back. :)
>
> Doug
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFIQJgq3LTjmOMguVMRAntVAKCALgvVnRpS5wo+i1m4G48TPJ6eXACfQJ+S
> ODuyJntHhxXDBqy/5DG2s6w=
> =mGI1
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org