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

  • Max-P@lemmy.max-p.me
    link
    fedilink
    arrow-up
    5
    ·
    5 months ago

    I guess the hostname could be used to defeat MAC randomization if you use public WiFi like hotels, airports and coffee shops. You could probably identify repeat users if you cared enough.

    But then your worry should be the security cameras not the WiFi, because that’s what’s gonna tie you personally to your device connecting.

      • Bitrot@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        2
        ·
        5 months ago

        You need to say more than that about what your concern is, especially on devices configured for Mac randomization and other privacy features.

        Aruba is looking at the dhcp traffic and inferring information about the device. The device is not sending all of this data.