As part of my standard (and pretty lame) OPSEC I always change the default names that apple gives its devices (like "Joiqj's iPhone") to a more generic name (like "iPhone"). Nice to see that it was good practice.
That reminded me that almost 10 years ago ghacks [1] instructed people to add _nomap to their Wifi networks name to avoid these being harvested by Google and Mozilla. I wonder if that ever worked or still does and if companies stopped collecting that information. [1] - https://www.ghacks.net/2014/10/29/add-_nomap-to-your-routers...
Brute-forcing a macOS user’s real name from a browser using mDNS
101–110 of 168 posts
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#102On my macOS box, I run Little Snitch, a nice UI that can be set to ask local user for explicit permission before allowing a network request. https://www.obdev.at/products/littlesnitch/index.html I’ve occasionally stumbled on it during remote logins, usually when an SSH session wants to download something new, like NPM requesting NodeJS bits. The text terminal SSH download will block; if I figure out it’s the Little S…
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#103Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#104I don't get why they resorted to the timing approach when they could just check the error message.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#105Earlier quoted context omitted.
It might sound a bit silly, but I've had pretty good results just naming my devices after Pokemon. Whenever I have a new device, I open the Pokemon DB[0], choose one at random, and then add it to my .csv file of device names -> what they are and what role they perform. [0]: https://www.pokemon.com/uk/pokedex
Rather than choosing at random, I like to pick names that have some relation to the device in question, e.g. "Pichu" for a tiny mobile device, "Snorlax" for the big slow machine, "Articuno/Zapdos/Moltres" for three successive powerful servers, etc. What's extra fun about Pokemon, if you're familiar with the franchise, is that you can pick names based on generation, with older generations for e.g. older devices, and i…
At work, let's just call things what they are.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#106Earlier quoted context omitted.
It might sound a bit silly, but I've had pretty good results just naming my devices after Pokemon. Whenever I have a new device, I open the Pokemon DB[0], choose one at random, and then add it to my .csv file of device names -> what they are and what role they perform. [0]: https://www.pokemon.com/uk/pokedex
I do the same thing but with Star Trek words! I have a somewhat logical naming scheme too. Computers are named after Star Trek ships (Yorktown), phones are named after handheld devices (Phaser), and drives are storage related things (Isolinear). And my printers are just named Replicator and Synthesizer.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#107The more time passes, the more comfortable I feel about mostly interacting with the internet from a Qubes box, in a disposable Whonix/Tor VM, with Javascript disabled... This is just gross. I mean, not surprising. But appalling in so many ways that it's even possible. If you're not familiar with fingerprint.com, they do "deep user profiling" - think "maintaining a constant user ID across computers, browsers, OSes, et…
Wow it totally recognizes my same device across different VPN IPs. Creepy indeed
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#108Earlier quoted context omitted.
Rather than choosing at random, I like to pick names that have some relation to the device in question, e.g. "Pichu" for a tiny mobile device, "Snorlax" for the big slow machine, "Articuno/Zapdos/Moltres" for three successive powerful servers, etc. What's extra fun about Pokemon, if you're familiar with the franchise, is that you can pick names based on generation, with older generations for e.g. older devices, and i…
My company uses codenames like this for our services and it drives me insane every time I have to go look up which is which or mentally convert to the name it should have been given. At work, let's just call things what they are.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#109Earlier quoted context omitted.
Wow it totally recognizes my same device across different VPN IPs. Creepy indeed
In my tests it only recognizes the same browser. I’m a different person when using different browsers. I noticed that I can still be correctly fingerprinted after resetting the browser or using a private window.
I haven't tested it, but presumably they also wouldn't be able to track me between domains, even without clearing cookies.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#110Earlier quoted context omitted.
In my tests it only recognizes the same browser. I’m a different person when using different browsers. I noticed that I can still be correctly fingerprinted after resetting the browser or using a private window.
Using Firefox (on a Linux laptop) with resistfingerpriting=true or Mull (on an Android) with its default settings, I'm able to get assigned a new fingerprint whenever I clear cookies or use a new Incognito session. I haven't tested it, but presumably they also wouldn't be able to track me between domains, even without clearing cookies.
Tor works for blocking it.
All in all they have created a creepy wee tool.