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

Privacy

30012 readers
1291 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 4 years ago
MODERATORS
k_o_t@lemmy.ml
tmpod@lemmy.pt
Yayannick@lemmy.ml
ranok@sopuli.xyz
5
Privacy concerns with DHCP (DHCP fingerprinting) (lemmy.zip)
submitted 1 week ago* (last edited 1 week ago) by possiblylinux127@lemmy.zip to c/privacy@lemmy.ml
43 comments fedilink hide all child comments
 

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
[–] Max_P@lemmy.max-p.me 2 points 1 week ago (2 children)

Most modern operating systems randomize the MAC. DHCP does have extra fields such as the device's hostname that can be used to counter that.

But as I said, that's unlikely to be the weakest link. If you don't trust the network you're also likely in a public environment where people can just see you anyway.

[–] user134450 4 points 1 week ago (2 children)

Most modern operating systems randomize the MAC.

[citation needed]
having the option to randomize the MAC is not the same as actually doing that. There are also a few downsides to random MACs, like captive portals not remembering you on public WiFis.

[–] Redjard@lemmy.dbzer0.com 2 points 1 week ago

The default on android is to give every wifi network its own random but static mac.

[–] delirious_owl@discuss.online 1 points 1 week ago

Captive portals not remembering you between sessions is a huge bonus for captive portals with time limits.

[–] 14th_cylon@lemm.ee 1 points 1 week ago (2 children)

Most modern operating systems randomize the MAC.

that doesn't seem to be uniform behaviour. but i think we agree on the merit. if you are this paranoid, you just don't use networks where you don't have control over the local segment.

[admin@MikroTik] > ip arp print 
Flags: X - disabled, I - invalid, H - DHCP, D - dynamic, P - published, C - complete 
 #    ADDRESS         MAC-ADDRESS       INTERFACE                                                    
 0 DC 192.168.88.160  A2:35:xx:xx:xx:xx bridge                                                       
 1 DC 192.168.88.159  F4:60:xx:xx:xx:xx bridge                                                       
 2 DC 192.168.0.1     44:32:xx:xx:xx:xx ether1                                                       
 3 DC 192.168.88.168  18:3D:xx:xx:xx:xx bridge                                                       
 4 DC 192.168.88.156  70:BB:xx:xx:xx:xx bridge

[–] ReversalHatchery@beehaw.org 1 points 1 week ago (1 children)

you just don't use networks where you don't have control over the local segment.

Easier said than done. Sometimes it's not an option.

[–] 14th_cylon@lemm.ee 1 points 1 week ago

there is always an option. unless you are pressured by lets say some state authority or your employee, in which case your identity is probably well known and they don't really need to spy on you through dhcp.