Out of date URLs, typos, changed IPs, canceled accounts, bad redirects, joke/troll links, etc. Simply 'accessing' a 'honey pot' means nothing. If you read them, you will notice multiple (consistent really) uses of the words 'knowingly' or 'with intend to defraud' etc. If you are interesting enough to warrant government level interest in your web browsing habits, you are beyond wondering whether it is legal for your landlord to let a neighbor have control of a wifi access point or for any user on the network to run wireshark.Īs for your mentions of CFAA, you're way overreaching. It provides both a privacy cut out (assuming the service does as you pay for and does not keep logs of your usage) and encryption that should be difficult enough to discourage anyone but state actors from trying to figure out your usage. For reasonable values of 'the future' a VPN can protect you to a reasonable degree. For short term values (as in weeks to months), you can of course, but we're already addressing that via the recommendation to either use a private internet link or VPN or both. You can't accurately predict what technology, features or methods of use people might employ in the future so trying to anticipate it is mostly a fruitless activity. ARP poisoning is probably the only method you could effectively detect, and the least likely to be used if the attacker controls your network. I think you'd be hard pressed to make an issue out of it.

Reading the contents of your traffic is scummy, but possibly legal. The situation is much better than it was 10 years ago though, by default the vast majority of traffic is encrypted effectively. A tool like cain and abel to audit your traffic for plaintext information could be revealing for you as well. Using a router with a wirless bridge to pipe all your traffic through said VPN would be ideal here. VPN services are cheap, as is rolling your own solution with a VPS. Taking the standard precautions is advisable.

Your security situation is about as good as a coffee shop or library. They can correlate HTTPS traffic to services based on IP, and sometimes the HSTS header, but the HSTS header doesn't need to be accurate. Yes they could get the contents of your DNS traffic, this tends to be plain text. If they control the gear, then monitoring a mirrored ethernet port or just straight up dumping traffic via netflow or similar from the router are also possible. ARP poisoning is another method for collecting traffic that is effective. De-authing all clients to force a handshake when starting monitoring is also trivial. Yes you need the EAPOL handshake, but that is trivial and automatic when using airmon-ng (most common tool for listening to wifi).

You could demand the landlord enables AP isolation (this prevents wireless clients from routing to each other, and usually also to the ethernet switch), which would add an additional peace of mind or, for best paranoia-mode-enabled, use an off-site VPN endpoint. I'm not aware of many consumer grade routers even capable of this. Your assertion that domain names and HTTP plaintext can be captured is false - The router itself would need to be doing a port mirror from the WiFi AP to an ethernet port, and if this is the case, the router is compromised and must not be used. a laptop on the router's wired ports) will see is things like ARP packets and other broadcasts. It's not a difficult thing to do, but it's certainly non-trivial.Įven if the attacker is on one of the router's ethernet ports, all any Wireshark device (e.g. To monitor another client you need to do an attack on the 4-way handshake when the per-client key is changed. A client on a WPA2 protected WiFi should not be able to see the traffic of any other client with Wireshark.

Is wireshark safe and legal