$718K penalty against M.C. Dean for blocking Wi-Fi devices (2015)
transition.fcc.gov
transition.fcc.gov
Android's built-in hotspot functionality still doesn't support this at all, and hotspots are the main thing here being targeted by hotels. If you want to see this fixed in Android, consider starring this issue: https://code.google.com/p/android/issues/detail?id=197440
It's left me scratching my head as to why a protection mechanism such as this isn't mandatory by now. Because mandating aspects of the protocol seems to be the only sure way of easing compatibility woes.
This kind of attack is really easy to make just by setting up a wireless network with the ssid you want to block and starting wireless containment countermeasures for rogue ap detection.
>But because of the shared, "commons" model that applies to all unlicensed operations, the Commission has >repeatedly held that "interference caused to a Part 15 device by another Part 15 device does not constitute >harmful interference."
In other words because the spectrum is unlicensed and because the transmissions were conformant with the part 15 spec, any such operation following the spec is allowed. How they can then they find that the Hotel was causing harmful interference is a bit troubling.
Clearly in everyday language we could describe what the hotel were doing as harmful, but the whole point of unlicensed spectrum is that it's a commons free-for-all. When wifi gets degraded to usability at trade shows because everyone's wifi is interfering with each other, nobody calls the FCC and files complaints about harmful interference.
Also it appears the FCC have been previously explicitly asked if deauth broadcasts like this are disallowed, and specifically chose not to make a ruling. It makes me wonder what the heck is going on over there. Has this issue become a political football between different factions over at the FCC?
47CFR15.5(b) talks about transmit and receive. People intentionally mis-interpret the receive section as somehow referencing transmission. The transmit side is as follows: "Operation of an intentional ... radiator is subject to the conditions that no harmful interference is caused"
47CFR15.3(m) Harmful interference. Any emission ... that ... seriously degrades, obstructs or repeatedly interrupts a radiocommunications service operating in accordance with this chapter.
It is true that on the receive side you have no legal protection according to 15.5(b). However transmitting a jamming signal is quite illegal.
Its very strange, like imagine two laws, one says its illegal to shoot at people, the other says you have no legal protection if you stand in front of a bullet. Then everyone exclusively quotes the latter stating its perfectly legal to shoot people, despite the former explicitly prohibiting that specific act.
The FCC doesn't send men in black in vans when people interfere with aircraft navigation for fun or because they're nice guys, although they are, but because they're legally obligated to do so because those parts don't have "too bad so sad" written into the legal code. All the "you're screwed if you're interfered with" in part 15 means is the FCC is not legally obligated to send in the men in black suits and vans solely for part 15 complaint issues. It doesn't mean interference is legal under part 15 rules, in fact the line right next to it explicitly states it is not legal and if by some miracle you're caught you are in big trouble.
This could be similar to some type of wifi blackmail. I could rent an apartment in expensive complex and setup a wifi jammer. then approach tenants that i can turn it off for X amount per month.
using != jamming
Over in the ham space if you know you're causing interference you're required to back off, regardless of who was there first(excluding some emergency situations).
It's the difference between not being able to talk to someone because you're in a crowd and not being able to talk to them because someone is standing behind you screaming into your ear.
That said, I guess you'd have to see what those specific repeated rulings were and for example whether they were two neighbors bickering over a network or convention centers blocking all WiFi except their own.
If I use WIFI as it's intended there's no mens rea. If I misuse WIFI to block your access there is mens rea.
Interesting article from spring 2016 http://www.networkworld.com/article/3042454/mobile-wireless/...
> Marriott admitted that the Wi-Fi users it blocked did not pose a security threat to the Marriott network.
> Similarly, Smart City submitted no evidence that the deauthentication was done in response to a specifically identified security threat.
It seems to me like it might still be okay to use WiFi deauth to automatically defend your network against security threats, such as foreign APs advertising the same SSID as your network?
What they're saying is that you can't actively interfere with parties who want to use unlicensed spectrum to communicate with each other, even if they are physically on your property, and the fact that you must share bandwidth with them is not a valid excuse to do so.
Since no one owns the frequencies no one owns the SSIDs and there is no way to specify who is the legitimate user and who is the adversary. The only solution is if any one party just does not interfere in the business of the other.
For example you can't block all "Netgear WLAN" hotspots, but you can block all "Hotel Sunrise NY Guests" networks. And you can not block SSIDs similar to your private network simply because you are too lazy to specify the routers MAC in all your five devices.
But what if we are "Hotel Sunrise NY Guests"? Why wouldn't i use that name as a guest? I think if you want defensible randomization, you actually randomize it.
If you walk into Hotel Sunrise and start walking up to people and saying "I'm with Hotel Sunrise Guest Satisfaction, can I ask you some questions?" the defense "Well, I'm a Hotel Sunrise Guest and it was for my Satisfaction!" is not going to absolve you of any consequences that arise.
Actually, that's a completely different issue.
I think that because the area involved is so local, the FCC is optimistic unlicensed spectrum users can come to consensus on that matter, otherwise it's going to have to deal with it in the more explicit, costly, and user inconvenient manner that it has done so in the past with identifiers used over less locally constrained, longer wavelength frequencies.
I think optimism is warranted. If someone local to you is being a dick with your SSID, you use technical (protocol level) countermeasures to disrupt them. This has been standard practice for a decade. If the attacker uses those countermeasures against legitimate users, apparently the FCC is now willing to respond with financial countermeasures against the attacker if it can.
If there were somehow a situation where the FCC was technically unable to respond, like say the attacker had a swarm of invisible drones equipped with access points advertising your SSID, then it would be helpless. The only solution would be to wait for vendors to come together through the IEEE or IETF with a standard to thwart the evildoers. (Probably years)
And it may yet come to that. But for now, the FCC clearly represents, at least within the United States, that corporate evildoers cannot blatantly perpetrate denial of service attacks on public spectrum without fear of sanction.
There was quite a bit of talk about this in the WIPS industry after these fines, and while I don't think the FCC has really made a clear clarification on the issue, the vendors have all put out statements that are similar variations on "it's okay for matching SSIDs" and I don't think there has been any contest to this. Vendors do recommend that you be careful that active mitigation will not impact APs operating off your property, implicitly even if they are broadcasting your SSID.
In general I think the FCC is taking an intent approach to this, from the security side - their rulings on WiFi jamming cases have generally specifically mentioned the lack of a reasonable security justification.
Trademarks, Fraud, etc could be the legal basis for this.
Take the ham operator scenario: One operator can't broadcast a continuous whistle so that nobody else can talk. It's impossible for an operator to obtain consent to do this. A hotel acting as an operator can't do it even if they got permission from every guest because the guests don't have any authority to grant it. It's simply prohibited for any operator to behave that way, full stop.
There are a couple of things a hotel could do though:
1) Kick anyone using wifi in a way they don't like off the property.
2) Encase the exhibition area in a giant Faraday cage so that nobody's cell phone works. Their APs are the only ones with internet access so no point for anyone else to turn one on.
I don't think either option would end well for any business that tried it. The reason they like the deauth method is because they can lock out competitors without the non-technical public realizing what's going on.
Also, the FCC determined that those clowns were jamming the Wi-Fi of buses passing the convention center.
Similar to the fact that you can not agree to someone taking you as a slave. It is still illegal.
edit: Imagine if this convention center entered into an exclusivity agreement with Verizon, then jammed the frequencies used by the other cellular carriers. Would that be OK?
But I can lawfully use my own WiFi hotspot, even while I am lawfully on your property. You may own the property, but you do not own the radio spectrum.
Imagine you're at a hotel, you can access their WiFi but you have to pay for it. Imagine you're at another hotel, you can use their pool but you have to pay for it. Are you being extorted? No. That's a better example.
Less glib, sure I doubt the FCC would care at all if they weren't spamming passerbys.
Wireless spectrum is one of those things.
Furthermore, even if the building was a perfect Faraday cage, there are other issues, such as the laws governing public accommodations, and the special scrutiny imposed on "contracts of adhesion" (take-it-or-leave-it standard form contracts) when analyzing them for unconscionability, plus the FCC's mandate which doesn't stop at property boundaries and generally can't be overridden by private contracts anyway. It's not clear that it would be allowable even if you set aside the near-certainty of interference outside the property of the interferor.
the agency regulates the spectrum, and nobody else, the spectrum is not my or from the hotel, so i cannot agree that they can block it or not.
Contracts cannot override the law.
Indeed, but they can stipulate other consequences.
For example in current $WORKPLACE, being found to operate an unapproved wifi AP will result in a disciplinary action. Too many of those and dismissal follows.
In current $WORKPLACE, being found to murder children will result in disciplinary action. Too many of those and dismissal follows.
So, the dismissal matters not at all, murdering children is the underlying problem. It's illegal and no contract can make that ok.
Conversely using a mobile phone to make a phone call is legal, but it's not allowed on the trading floors of banks. So it can be legal to refrain people from performing some legal activities on your premises. So I think a hotel probably can ban guests from operating a wireless AP, but jamming such activity using active measures is going too far.
Chucking a "you can't bring your own WiFi [because we want to make more money selling it to you]" term into the standard language on a hotel agreement might have a much harder time passing muster.
Further, there's a lot of caselaw built up over time that treats dwelling places, even temporary ones like hotels, differently than workplaces. (E.g. it's perfectly fine for your employer to set up cameras in your office to keep an eye on employees, but if a hotel did that in guests' rooms they'd have a problem on their hands, and I strongly suspect that wouldn't change even if they put some "you consent to be photographed!" small print on the check-in agreement along with the no-smoking policy and other boilerplate.)
Exactly. It's the jamming which is illegal, not the ban.
That's so outrageous.
> Marriott agreed to settle the investigation by paying a civil penalty of $600,000 and establishing operating procedures to ensure that it does not engage in further Wi-Fi blocking
Presumably MC Dean did not.
They were actively harming/disrupting others' equipment. It wasn't just "oh, your signal sucks, use ours!" but "we're going to knock you offline unless you pay."
Disclosure: I used to work for MC Dean 10+ years ago.
Now, they probably should have pushed back and advised the owner that what they wanted was illegal, but I'm sure it wasn't their idea. They don't own the building or host the conferences, so why would MC Dean care who uses which Wifi?
If there was a deal like that in place, it would be motivating to disrupt the alternatives.
Believing that a company is not liable for an illegal act they are hired for shows just how far the rabbit hole modern society has gone with respect to business ethics.
AFAIK (and IANAL) in the USA (IANAL in other countries either :)), some areas even criminalize the act of intentionally joining an open wifi, so I imagine a court could be extremely broad in its definition of "interfere" -- in our technophobic atmosphere, I wouldn't be shocked if this extended to scanning for SSIDs outside of the context of the OS.
They used it on other people's networks and their wifi APs. If they only DoSed their own APs, no one would care. You are allowed to DoS your own APs.
Nothing has changed though, those laws have been in place since soon after the invention of radio.
For example, a movie theatre, airport or hospital could all have good reasons to block radio signals.
Let's say I observe two ham radio operators having a morse code communication. I decide to stop them from communicating, so I transmit "<callsign 1> QRT DE <callsign 2>", where callsign 1 and callsign 2 are the callsigns of the two ham radio operators.
Is this harmful interference, or did one of the ham radio operators just misinterpret my signal?
I decide to stop them from communicating, so I transmit "<callsign 1> QRT DE <callsign 2>"
Is this harmful interference?
On amateur radio, you're obliged to identify yourself, so this would be a breach of licence: failing to identify your station, or misrepresenting your station.From what I understand of this attack, the signals are not being misinterpreted. The client receives a packet which basically says "I'm the AP and want you to disconnect", so the client correctly does what the packet asks it to. The packet, however, was spoofed; who send it was not the AP, but someone else.
The solution to this particular attack, as someone else mentioned, is 802.11w, which authenticates these control packets so they can't be spoofed. Unfortunately, it's still uncommon.
Will we soon be banned from using red light bulbs at home, because their wavelength is illegal?
Some spectrum is licensed. Some is for public use, such as WiFi, Bluetooth, baby monitors, and many other uses.
How would you like it if someone else on their own private property interfered with your use of WiFi on your property by sending you deauth packets?
I pay AT&T for my phone, including the use of it as a hotspot. AT&T paid handsomely to license the spectrum it uses to provide service to my phone. I'm sure they would not be happy if I am unable to use that service because I am maliciously blocked by someone interfering with my lawful use of WiFi spectrum on my own lawful hotspot, regardless of what property I am lawfully on, such as a hotel.
There always is. Radio waves don't respect walls (unless they're made of metal). If you look at the linked document, it shows strong indications that the attacks did affect wifi networks from vehicles passing by, that is, fully outside of the property.