So many people here will go though great lengths to protect themselves from fingerprinting and snooping. However, one thing tends to get overlooked is DHCP and other layer 3 holes. When your device requests an IP it sends over a significant amount of data. DHCP fingerprinting is very similar to browser fingerprinting but unlike the browser there does not seem to be a lot of resources to defend against it. You would need to make changes to the underlying OS components to spoof it.

What are everyone’s thoughts on this? Did we miss the obvious?

https://www.arubanetworks.com/vrd/AOSDHCPFPAppNote/wwhelp/wwhimpl/common/html/wwhelp.htm#href=Chap2.html&single=true

  • irq0@infosec.pub
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    I feel like I’m missing something here…

    Who’s going to be fingerprinting DHCP messages on your home network?

    Outside of that, fingerprinting or tracking any DHCP info would be the least of my concerns. You have 0 control over any data the moment your devices connect to a public network. What use is DHCP info when you can person-in-the middle all the traffic anyway?

    And anyway, what info are you concerned about? Having had a VERY quick browse of RFC2131 the worst thing would be “leaking” the device MAC address which can be discovered via several other means anyway