On 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…
In my case, I couldn't imagine configuring LittleSnitch to only allow certain hostnames from my browser. It has a "allow all traffic to 53/80/443" rule, otherwise most websites would flood me with hundreds of new LittleSnitch popups.
Brute-forcing a macOS user’s real name from a browser using mDNS
61–70 of 168 posts
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#62Earlier quoted context omitted.
In my case, I couldn't imagine configuring LittleSnitch to only allow certain hostnames from my browser. It has a "allow all traffic to 53/80/443" rule, otherwise most websites would flood me with hundreds of new LittleSnitch popups.
You'd think so, but the way I've set it up Little Snitch throws up a dialog box when a browser makes errant requests but otherwise remains silent. Most recently this caught Firefox trying to force DNS over HTTPS despite me having disabled it when it first became generally available. I suppose leaking DNS requests to Cloudflare isn't the worst thing in the world, but it would circumvent the ad blocking I've set up loc…
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#63On 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…
It's surprising what sneaky socket connections applications connect too; including bank apps.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#64As 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.
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#65Is there a way to prevent websites from the broader Internet from making network requests to my local network? I can't imagine why this should be allowed by default. (Not to suggest bringing back IE's Local Intranet Zone permission...)
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#66Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#67Is there a way to prevent websites from the broader Internet from making network requests to my local network? I can't imagine why this should be allowed by default. (Not to suggest bringing back IE's Local Intranet Zone permission...)
uBlock Origin static filter: ||local^$all This will block all requests to .local, even from .local itself. If you want to allow foo.local to talk to itself, say because you run a webserver on it, you'll have to add additional overrides for each such domain: @@||foo.local^$domain=foo.local,all ... or if you trust your .local entirely to allow any foo.local to talk to any bar.local, you can add one override for all of…
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#68Is there a way to prevent websites from the broader Internet from making network requests to my local network? I can't imagine why this should be allowed by default. (Not to suggest bringing back IE's Local Intranet Zone permission...)
uBlock Origin static filter: ||local^$all This will block all requests to .local, even from .local itself. If you want to allow foo.local to talk to itself, say because you run a webserver on it, you'll have to add additional overrides for each such domain: @@||foo.local^$domain=foo.local,all ... or if you trust your .local entirely to allow any foo.local to talk to any bar.local, you can add one override for all of…
Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#69Re: Brute-forcing a macOS user’s real name from a browser using mDNS
#70As 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.
A lesson learned with early feature phones and Bluetooth names in high school
At home my wifis are currently Japanese emojis, but anything funny goes