Re: socket programming and port scans

2005-05-19 Thread Peter Hansen
rbt wrote: > I don't fully understand sockets, I just know enough to be dangerous. > The below is not detected by nmap, but is affected by iptables or ipsec. > Can anyone explain why that is? > > s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) > s.bind((ip_param, port_param)) >

Re: socket programming and port scans

2005-05-18 Thread rbt
millerch wrote: > Are you explicitly referencing the port for nmap, or is it a general > port scan? > > The version of nmap I run only checks common ports unless a port range > is specified. I did not know that. It works as expected now. Thanks! -- http://mail.python.org/mailman/listinfo/pytho

Re: socket programming and port scans

2005-05-18 Thread millerch
Are you explicitly referencing the port for nmap, or is it a general port scan? The version of nmap I run only checks common ports unless a port range is specified. rbt wrote: > I don't fully understand sockets, I just know enough to be dangerous. > The below is not detected by nmap, but is af

socket programming and port scans

2005-05-18 Thread rbt
I don't fully understand sockets, I just know enough to be dangerous. The below is not detected by nmap, but is affected by iptables or ipsec. Can anyone explain why that is? s = socket.socket(socket.AF_INET, socket.SOCK_STREAM) s.bind((ip_param, port_param)) while 1: s.l