Re: naming the boxes in a DHCP net
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Fri, 27 Oct 2006 20:57:04 -0500
On 27 Oct 2006, in the Usenet newsgroup alt.os.linux.suse, in article
<1161965124.033784.258290@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, jjgitties wrote:
If this is exposed, don't name them anything that would give out
information such as OS version.
You're posting from google, which is a search engine. Use that, and search
for the term 'O/S fingerprinting'
Web Results 1 - 10 of about 63,600 for O/S fingerprinting. (0.91
Who knows - you might be amazed at the results.
I also like to take it a step further and not try to divulge too much
of the network setup. i.e. when you so a scan and you see.
[rather lame names - I agree]
You know damn well where the sys admins and where the server is and
what to avoid and what to aim for. if you have a naming convention,
them try to stick to it. note: naming the server does make sense but
try to blend in the other host such as admin machines and other
In a well designed network (which means a firewall), you're probably not
going to see that many names. Where I work, internal hosts can see the
internal names. External users can only see those crap generic hostnames
that are "hostname-IP-ADD-RE-SS" whether or not there's a host at that
IP or not. The only company names that resolve externally to "real" names
are the systems in the DMZ.