Operating Broadcom Wi-Fi Chips as Arbitrary Signal Transmitters, Like SDRs
github.com
github.com
Matthias Schulz, Jakob Link, Francesco Gringoli, and Matthias Hollick. Shadow Wi-Fi: Teaching Smartphones to Transmit Raw Signals and to Extract Channel State Information to Implement Practical Covert Channels over Wi-Fi. Accepted to appear in Proceedings of the 16th ACM International Conference on Mobile Systems, Applications, and Services, MobiSys 2018, June 2018.
Matthias Schulz. Teaching Your Wireless Card New Tricks: Smartphone Performance and Security Enhancements through Wi-Fi Firmware Modifications. Dr.-Ing. thesis, Technische Universität Darmstadt, Germany, February 2018.
But the papers are nowhere to be found. Just went through peer review and still waiting for public publication?
Edit: + covert channels
might be coming soon. Feb 2018 is pretty recent, and publication is sometimes delayed due to procedural issues. However, it might just be "published" by having a number of copies in the university's (as well as the state's and German federal) libraries.
Moreover, there are plenty of radios on the market that transmit all kinds of noise on these channels that isn't WiFi (e.g. my neighbors had a baby monitor that I could tell when it was on by how shit my WiFi was at that moment, FPV drones somewhat frequently use this band with proprietary analog video transports, etc.) This is permitted because these channels are "unregulated" (or, more realistically, "regulated for unlicensed operation").
On top of that, the FCC's official statement on this very topic was that what they really care about is the amount of power being put into these channels, as some aftermarket router firmwares of varying repute would let you crank the output wattage above FCC regulations for these frequencies (<1W power to stay within unlicensed operation regulations for 2.4GHz), and apparently some in-market WiFi routers picked up those firmwares as a "supported" option (I think ASUS and Linksys were both named). Most of these routers have since patched themselves to stay regulation-safe.
So, go nuts, just stay below 30 dBm/1W from the transmitter in 2.4Ghz channels or prepare for a visit from the FCC. (You'll have to do your own research for 5GHz).
I realize they're probably terrible quality, and that they're really just Wi-Fi dongles with amplifiers tacked on, and that overly loud signal amplification destroys close range performance - but still, I'd been meaning to get a couple of these and see how good they are.
So
This 5MW one: https://www.ebay.com/itm/171907612288
And this 5.8MW one: https://www.ebay.com/itm/222605454974
And this 6MW one: https://www.ebay.com/itm/171907483813
Are all 2.4GHz.
And I probably shouldn't really use any of them then. :/
They would be legal for a point-to-point setup, since they achieve their high EIRP due to high antenna gain (as opposed to high output power). But also due to that high gain, they're not really useful for anything but point-to-point (think backhaul between buildings).
You could also use them legally and usefully as a client (pointed at an AP) if you turn the power down so that the EIRP is 4 W (36 dB). You'd still benefit from the high antenna gain in the receiving direction (though not in the transmitting direction, which includes TCP ACKs).
Interfering with licensed radar installations would seem to be a legitimate problem.
[1] http://www.ieee802.org/18/Meeting_documents/2007_Nov/WFA-DFS...
It would be based on both their GPLv3 and their no-military licenses simultaneously. The linked requires another depot based on GPLv3 to function and perform patching. The resulting software would then undistributable as you cannot possibly comply with both the GPLv3 and their no-military license. GPLv3 would permit distribution to military and not permit you to restrict them and the other would prohibit military.
Additionally this should be considered a violation of Gitbub's Terms of Use. It is intentionally discriminatory against another group: Any given military. For example, the content hosted on GitHub is intentionally discriminatory toward the Deutsches Heer.
Unfortunately I don't think some people could ignore the potential for abuse. If only I could be 15 feet to the left where the other guy's crappy GPS puts him. At some point I'm hoping my city will put up a few WAAS transmitters to help in the glass canyon that is our downtown.
http://www.datasheetspdf.com/datasheet/download.php?id=73999...
The combo chip itself probably has multiple SDRs internally so that e.g. you can use GPS and WiFi/BT simultaneously, but they can be connected externally to the same antenna through a diplexer.
https://2016.mrmcd.net/fahrplan/system/event_attachments/att...
RaspberryPee wifi chipset (BCM43438) is a close cousin and previous work (monitor mode, sending raw frames) was ported last year.
https://dev.seemoo.tu-darmstadt.de/bcm/bcm-rpi3/tree/master/...
so there is a chance this could to, it would mean $30 self contained 2.4/5 GHz SDR.
Imagine someone wanted to, say, provide native support in GNUradio - as has been done for the RTL-SDR. It's impossible unless you relicense one or the other.
Of course, the code's being given away for free; you could argue one shouldn't look a gift horse in the mouth. And it's quite possible no-one would attempt such a merge even if it was permitted by the license.
[1] https://en.wikipedia.org/wiki/License_proliferation#License_...
- The one you mentioned about citation.
- “The Software is not used by, in cooperation with, or on behalf of any armed forces, intelligence agencies, reconnaissance agencies, defense agencies, offense agencies or any supplier, contractor, or research associated.”
https://github.com/seemoo-lab/mobisys2018_nexmon_software_de...
Even just the one about citation is problematic but IMO the condition about armed forces and so on is even worse. I kind of see where they are coming from but I wish people just used standard MIT and acknowledged that yes your software might end up being used for something that you do not agree with morally.
And if they are going to impose such restrictions, why stop there? Why not also say that you cannot use the software to transmit for example child pornography? And how about saying that you cannot use it to spread false information, fake news etc?
I would be exaggerating, but not much, if I were to say that as soon as you introduce one or more moral restrictions into a software license, you are implicitly saying that any moral concern not mentioned is ok.
How about terrorism? They didn’t say anything about terrorism so I guess using their software for terror is fine as long as the terrorists are not an “armed force”, an intelligence agency etc.
Technology has infitinite uses, a whole host of which are good, probably as many that are bad, and likewise an uncountable amount of uses that are either neither or both, and very many that will be one thing for some people and the other for other people.
It should in my opinion not be the job of a software license to pass moral judgement. Either you release your software for anyone to use for any purpose under the terms of an unmodified license accepted by the community or you might as well not bother trying to be open source at all.
Because it's already illegal, so the point would be a noop. On the other hand, contracting for the army is legal and one of the places where licenses may be reviewed/enforced internally.
Same for terrorism. (Also, why would terrorists respect the license)
The MIT licence doesn't prohibit you from rewriting it and changing it to something else and the community isn't a monolith.
A lot of people don't want any of their work associated with military purposes. If someone wants to use the code but falls foul of the licence then they should just look elsewhere.
With the same logic it can be argued that is not your job to decide what a software license is for.
Instead, it's the author prerogative to release software with any license they can think of.
It's up to distributions, other developers and users to decide what to do with it.
Most distributions will not package and distribute software under licenses that create gray areas and are difficult to enforce - not because of moral judgments.
https://en.wikipedia.org/wiki/Debian_Free_Software_Guideline...
Because that is illegal. They excluded legal use cases, and as far as I'm concerned excluding uses for military reasons is all right.
How does this work compare to gaining (similar) access to the baseband processor on a phone ?
There should be a bounty for that ...