Musician, mechanic, writer, dreamer, techy, green thumb, emigrant, BP2, ADHD, Father, weirdo

https://www.battleforlibraries.com/

#DigitalRightsForLibraries

  • 15 Posts
  • 120 Comments
Joined 1 year ago
cake
Cake day: June 13th, 2023

help-circle
  • I used to provide commercial end-user support for a network intelligence product that used as much metadata as possible to help classify endpoints, shuffling them off to the right captive portals for the right segment based on that data.

    I can tell you that the things you’re saying are transmitted in a DHCP request/offer are just not. If they were, my job would’ve been a LOT easier. The only information you can count on are a MAC address.

    I can’t view that link you shared, but I’ve viewed my share of packet captures diagnosing misidentified endpoints. Not only does a DHCP request/offer not include other metadata, it can’t. There’s no place for OS metrics. Clients just ask for any address, or ask to renew one they think they can use. That only requires a MAC and an IP address.

    I suppose DHCP option flags could maybe lead to some kind of data gathering, but that’s usually sent by the server,not the client.

    I think, at the end of the day, fighting so that random actors can’t find out who manufactured my WiFi radio just isn’t up there on my list of “worth its” to worry about.











  • No, you’re absolutely right. That’s what happens when you have the WaaSMedic service running, which cannot be easily disabled in services.msc. I would think I had finally gone the “full-nuclear” option and broken al updates by disabling and stopping the update services (that I knew about), but they would re-enable themselves without fail.

    This comment explains where you need to disable it (if you want to go that route).