4
Privacy concerns with DHCP (DHCP fingerprinting)
(lemmy.zip)
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.
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
DHCP only acts in local networks which is in 90%:
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:
Also take note some general location tracking can already be done through mobile networks.
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.
But the reasoning stays the same.
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?
No, you may have to re-login every time you connect, but once you connect, your MAC would be stable for that session.