Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was trying to check a host say (www.mydomain.com) using nmap. There basically i should get something like...
Code:
[root@test root]# nmap www.mydomain.com
Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2007-08-24 21:39 UTC
Interesting ports on www.mydomain.com (2.2.2.2):
(The 1656 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
53/tcp open domain
80/tcp open http
111/tcp open rpcbind
443/tcp open https
3306/tcp open mysql
Nmap finished: 1 IP address (1 host up) scanned in 0.177 seconds
But i get something like this:...
Code:
[root@test root]# nmap www.adomain.com
Starting nmap 3.81 ( http://www.insecure.org/nmap/ ) at 2007-08-24 21:43 UTC
sendto in send_ip_packet: sendto(3, packet, 40, 0, 3.3.3.3, 16) => Operation not permitted
sendto in send_ip_packet: sendto(3, packet, 40, 0, 3.3.3.3, 16) => Operation not permitted
sendto in send_ip_packet: sendto(3, packet, 40, 0, 3.3.3.3, 16) => Operation not permitted
sendto in send_ip_packet: sendto(3, packet, 40, 0, 3.3.3.3, 16) => Operation not permitted
sendto in send_ip_packet: sendto(3, packet, 40, 0, 3.3.3.3, 16) => Operation not permitted
sendto in send_ip_packet: sendto(3, packet, 40, 0, 3.3.3.3, 16) => Operation not permitted
caught SIGINT signal, cleaning up
This seems to me that the server is very secured and i also tried other options like -sS -sU -v -O -D A.B.C.D
But same result... if this tells me that that remote server is a secured server (since i cant scan that even), then i wanna make my one like this... so others cant scan me using the same way... how??
well, let me explain more... I am sitting on 192.168.0.10 and i was doing nmap on 172.16.0.10
Now when i nmap myself, (192.168.0.10) it gives me results as usual...
but when i nmap 172.16.0.10, it gives me
sendto in send_ip_packet: sendto(3, packet, 40, 0, 172.168.0.10, 16) => Operation not permitted
Now, I dont know why this (172.16.0.10) is responding like this...(it responds to ping) but if this is a good sign of security (because i cant scan that 172.16.0.10) then how can i make my machine (192.168.0.10) exactly like that one (172.168.0.10) so others cant scan me....
Distribution: BeOS, BSD, Caldera, CTOS, Debian, LFS, Mac, Mandrake, Red Hat, Slackware, Solaris, SuSE
Posts: 1,761
Rep:
According to the changelog, that was supposed to be fixed in version 3.81:
"Changed IP protocol scan (-sO) so that it sends valid ICMP, TCP, and
UDP headers when scanning protocols 1, 6, and 17, respectively. An
empty IP header is still sent for all other protocols. This should
prevent the error messages such as "sendto in send_ip_packet:
sendto(3, packet, 20, 0, 192.31.33.7, 16) => Operation not
permitted" that Linux (and perhaps other systems) would give when
they try to interpret the raw packet. This also makes it more
likely that these protocols will elicit a response, proving that the
protocol is "open"."
This was found when i did the nmap to my server. Also when i do only "nmap www.mydomain.com" i get the same. And same for any other machines. what is it for??
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.