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.
0 kommentar(er)
