31–40 of 56 posts
Some buildings (hostels and shared accomodations) have shared internet (secured with WPA2). This type of attack might be particularly profitable in such situations.
Wouldn't WPA2 protect users from an attack like this?
Given the recently disclosed vulnerabilities, instead of a cryptocurrency miner, it could be a Spectre exploit trying to scan and exfiltrate data from the computer's memory. We might be now at the point where disabling all Javascript for non-HTTPS pages is a good default.
Earlier quoted context omitted.
Since we won't get https everywhere soon, is WPA2 on a public Wifi with a publicly known key a workaround? Should prevent plain MITM?
If you control the AP, you should disallow client to client communication. Most AP's and routers allow this and it would mitigate this risk.
Earlier quoted context omitted.
Is there any way to mitigate this without limiting abilities of people on the network? It kind of destroys the point of a LAN.
don't take my word for it, but I'd bet you could disallow LAN comms on port 80 and prevent this. Typically a toxic client would flood the arp table until the router believed the toxic client should receive all communications and then the toxic client would mitm and forward traffic on the expected port to other normal clients...if the toxic client can't send stuff on port 80 to a normal client they can't easily mitm t…
You could prevent wifi clients from communicating arp packets, I think that would allow most things to work.
If you have a corporate wifi system, you should be watching for arp poisoning anyway. If it's a public system, most people aren't using it to communicate between wifi devices. Most android devices that communicate via wifi will generate their own wifi network for the duration of the communication.
Earlier quoted context omitted.
If you control the AP, you should disallow client to client communication. Most AP's and routers allow this and it would mitigate this risk.
CoffeeMiner mixed with a WiFi Pineapple seems like the way to go.
Just give it the ssid 'xfinitywifi'.
I find it funny how, even after publishing this post, the author hasn't configured a http -> https redirect for his own site.
Earlier quoted context omitted.
Is there any way to mitigate this without limiting abilities of people on the network? It kind of destroys the point of a LAN.
Did you ever use LAN functionalities in public Wifi (e.g. Starbucks)?
Turned out he had crap taste in music and I ended up deleting my copy.
I've thought about adding something like this to my guest wifi to mine some cryptocurrency - but quickly dismissed it as most guests would need to use a charger soon(ish) and thus using my electricity :P