|
|
Hiding information from nmap - don't do it.
Don't do this if yyou do not exactly know what you gain by doing so and what you break.
Many things are designed in the assumption that you are notified if a port is closed. If your computer doesn't act accordingly you might break a lot of things. E.g. sending mail to certain servers or connecting to IRC (because of ident lookups/socks checks).
On the other hand most MacOS X computers can be identified without nmap. E.g. by checking HTTP headers:
[c0ldcut:~] md% telnet 127.0.0.1 80 Trying 127.0.0.1... Connected to localhost,. Escape character is '^]'. HEAD / HTTP/1.0 HTTP/1.1 200 OK ... Server: Apache/1.3.27 (Darwin) DAV/1.0.3 ...So fiddeling with the IP-Stacks internals has very questionable gains tto offer.
Hiding information from nmap - don't do it.
One should also be wary when giving bad information out.
Hiding information from nmap - don't do it if you think it will make you "more secure"
Use ipfw. And read the reply to the first "dont do it" post above. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.14 seconds |
|