5
submitted 4 months ago* (last edited 4 months ago) by possiblylinux127@lemmy.zip to c/privacy@lemmy.ml

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

you are viewing a single comment's thread
view the rest of the comments
[-] hostops@sh.itjust.works 5 points 4 months ago

DHCP only acts in local networks which is in 90%:

  1. home network where you trust every device to not spy on you
  2. office network where in most cases your emloyer provided you with the hardware. And in 10%:
  3. Public WiFi

The only thing leaked in DHCP is your MAC. Attacker can use this info to identify brand of our network adapter. Or if they have really huge database of laptop manufacturers attacker can identify your device. If you use VPN or TOR the only thing they know from now on is that you use VPN or TOR. And if they really have everything in that database they will be able to tell who bought that computer. So now attacker can only knows who is in their netwotk.

Which is useless in scenario 1. and 2. Where you already know who is in your network and owner of that network has no database to identify you based on your MAC.

In scenario 3. If we are talking about huge public networks like WiFi provided from your town. If infiltrated by 3 letter agencies which may have such database they could theoretically track your location based on which town network you connected to.

But you can protect yourself from this:

  1. Do not connect to public networks
  2. Your OS/Network card driver allow you to use random MAC address. Just enable random MAC in your network settings. In Android: WiFi > Select specific network > Privacy > Use randomized MAC.

Also take note some general location tracking can already be done through mobile networks.

[-] refalo@programming.dev 3 points 4 months ago

The only thing leaked in DHCP is your MAC

This is not true. It also leaks your hostname by default and often your previously associated IP. There's also vendor-specific "DHCP option" sets that can hold extra data too, which some OSes might use to leak additional info.

[-] hostops@sh.itjust.works 0 points 4 months ago

But the reasoning stays the same.

[-] schwim@lemm.ee 2 points 4 months ago

Does randomizing your MAC create any usability issues? Needing to log in repeatedly, getting bumped off network due to looking like a different device, anything else hindering usability?

[-] makeasnek@lemmy.ml 4 points 4 months ago

No, you may have to re-login every time you connect, but once you connect, your MAC would be stable for that session.

this post was submitted on 04 Jul 2024
5 points (61.9% liked)

Privacy

31876 readers
268 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS