OS fingerprinting based on TCP/IP and DHCP traffic

[anon]

Every operating system's TCP/IP stack has its own set of default values and extensions. Furthermore, a vendor ID string is sent when acquiring a network address via DHCP (option 60), and the padding and option layout on discovery packets make detection of a particular system possible even if said string is modified. Thus, it is possible to identify which OS a device is running merely by analyzing the above mentioned details. The following links, as well as looking for "OS fingerprinting" on your favorite search engine, provide more information, and means to (at least partially) shield yourself against this.

TCP/IP stack fingerprinting - Wikipedia, the free encyclopedia (http://en.wikipedia.org/wiki/TCP/IP_stack_fingerprinting)
fingerbank: Learn More (http://www.fingerbank.org/learn_more.html)
OSfuscate: Change your Windows OS TCP/IP Fingerprint to confuse P0f, NetworkMiner, Ettercap, Nmap and other OS detection tools (http://www.irongeek.com/security/osfuscate-change-your-windows-os-tcp-ip-fingerprint-to-confuse-p0f-networkminer-ettercap-nmap-and-other-os-detection-tools.htm)

[anon]

Two things I've learned since making this thread.

Under Windows, the registry key HKLM\SYSTEM\CurrentControlSet\services\Dhcp\Parame ters\Options allows you to define options that are sent in the DHCP discover packet. However, options 12 (hostname) and 60 (class identifier) cannot be set or overriden in this manner.
If you edit the value of "Hostname" and "NV Hostname" under HKLM\SYSTEM\CurrentControlSet\services\Dhcp\Parame ters\Options and restart the Dhcp service, it will use the new one for option 12 without having to actually change the computer name or reboot. However, I don't know which other side effects this may have.