Stuxnet/Flame/Duqu Uses GPL Code
David Gerard writes "It seems the authors of Stuxnet/Duqu/Flame used the LZO library, which is straight-up GPL. And so, someone has asked the U.S. government to release the code under the GPL. (Other code uses various permissive licenses. As works of the U.S. federal government, the rest is of course public domain.) Perhaps the author could enlist the SFLC to send a copyright notice to the U.S. government..."
That would imply that the government is ruled by law rather than the arbitrary decisions of a few "top men".
It doesn't take long for such attitudes to spread throughout society.
But hey, Obama said he would have, like, the totally most open presidency ever. Surely the new boss will prove himself different from the old boss in SOME way. Surely!
If you are already breaking laws left and right why would you bother to acknowledge copyright?
The people who released this have no respect for the law, and see themselves as above it they will not comply.
Under the GPL, only people that the executable was distributed to are allowed to request the code - and since it's a weapon, the US government isn't alliowed to send it to Iran.
Problem solved.
State sovereign immunity. Game over.
This involves the Mossad, CIA, and national security. You can ask, but you might not survive the attempt.
Gerald Bull and the drone attacks come to mind. Of course, this assumes that they even listen, and don't simply claim National Security!
No, selling or not selling is irrelevant. "Distributing" is the key.
LOLOLOL
What a stupid idea it was to go down that path. Now that the idiots in the us gov't have opened pandora's box, I'm sure we'll all soon have the opportunity to see the code up close and personal.
This whole thing is irrelevant due to state sovereign immunity. Good luck suing the government when they have to permit themselves to being sued.
So if this worm deploys itself onto a machine, it should deploy the source as well? Or, could it just deploy a link to the source, and since the software itself by its very nature tries to hide itself, could it hide the link?
Someone with gigantic balls of steel should file a FOIA on this basis.
It would be interesting to see if the request would even be acknowledged.
What makes the idea clever is that it's a public request (and publicise the hell out of it!) and it's powered by copyright. This is why the GPL is so effective...
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
Considering the "request" was just a joke post an obscure Hungarian blog, they will definitely be ignoring (read: never seeing) it.
Distribute, not sell. (Though you absolutely have the right to sell GPL code as well, as long as you abide by the rest of the license and release your source.)
In any case, I'm guessing that one of the following things will happen:
- Some sort of secrecy / national security provision is given as a reason source cannot be released (1% probability)
- Changes to the GPL portions are released (0.01% probability)
- Stone-cold silence (98.99% probability)
Remember, the US Government hasn't even acknowledged that they created these worms. We're still firmly in the "plausible deniability" phase.
It's better to vote for what you want and not get it than to vote for what you don't want and get it.
- E. Debs
The thing is, no one knows who wrote it. Sure, there is speculation that the U.S. and/or Israel did, but no one knows for sure. The simplest thing for the government to do is say "We can't because we didn't write it." Then, it falls on the asker to prove they did.
There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
Markus Oberhumer, author of LZO, also offers LZO Professional, a commercial version not subject to the GPL.
From http://www.oberhumer.com/opensource/lzo/lzodoc.php:
"Special licenses for commercial and other applications which are not willing to accept the GNU General Public License are available by contacting the author."
So our questions is: Please, Dear Authors of Duqu (whoever they are), hand over the source code of Duqu (or Beacon/NYT), as it contains GPL code.
Disclaimer: This post is for fun, don’t take it too seriously, but the questions are still valid.
Just as an aside, whenever some commercial entity finds itself in violation of the GPL, people start talking like they expect the code to magically be revealed and gifted to the community. This perpetuates the lie that the GPL is viral and can "infect" closed-source code. The reality is far different. If a company is found to be in violation of the GPL, they find themselves in a copyright violation situation. This means that they must a) stop further distribution and b) potentially be held liable for monetary damages resulting from the distribution. They absolutely don't have to release their code. However if they want to continue to distribute and sell their product they will have to do one of three things: 1) remove infringing code, 2) license the infringing code under acceptable terms, possibly by paying a licensing fee to the copyright holder, or 3) release their derivative code under the GPL.
Option #4: An obscure RFC describing the implementation of TCP/IP on a 5.56x45 'jumbo frame' physical layer is drafted.
and b) potentially be held liable for monetary damages resulting from the distribution. They absolutely don't have to release their code.
Unless the copyright owner of the GPL code offers to drop the claim for monetary damages in exchange for publishing the infringing code. As I understand it, this offer is routine for copyright infringement cases that involve the GPL.
The Federal Government has specifically disclaimed sovereign immunity in copyright cases under 28 USC 1498(b).
There may be other concerns, like national security that make it difficult though.
As an author of GPLed code, I've read the GPL license. It isn't possible for a random person, including the author of the GPLed works being distributed, to request source code. The only GPL provision for that is if the author distributes binaries of modified GPL code, at which point the author would need to distribute source code as well. Here's the sticky point, whoever requested source code wasn't the recipient of the binaries; therefore, they are not entitled to any source code. The authors of the GPLed source code are not entitled to it either, for the same reason. In fact, the only one who could demand (in theory at least) the source code would be the persons receiving the binaries containing the modified GPL code.
Then there's the point that bundling GPL software with your product doesn't necessarily mean that you're extending that product and therefore bound by the GPL. Not every piece of software compiled on/for Linux is bound by the GPL -- even if that software is distributed as part of a Linux distribution (i.e., bundled as part of a bigger package). Software that has an API and offers services to other software -- compression libraries, SQL, etc -- are expected to offer services to other software. Granted, some developers have taken the stance that if proprietary software works with only a specific GPL software (say, MySQL) and that particular GPL software is distributed with the proprietary software, that it violates the GPL, and a proprietary license is required. However, that is a developer stance, not necessarily a legal one.
So even if the government used GPL software (which may not be the case considering a non-GPL license is available for the software in question), it wouldn't necessarily be required to release any source code. There's a pretty good chance that it didn't change any GPLed source code -- even if it did bundle it with its own software and wrap everything up in a clever installer.
Under the GPL, only people that the executable was distributed to are allowed to request the code
As I understand the GPL, this offer must be extended to "anyone who possesses the object code" (GPLv3) or "any third party" (GPLv2). Anyone who has ever had a PC infected with any of these viruses "possesses the object code".
Precisely, and if someone writes a virus under the GPL, and only runs the virus, making it infect other computers that were not interested in receiving it, then is that considered a distribution of the binaries such that the source code has to be released?
Quoting the article because so far no one actually followed the link and read it (as usual).
Do they use a rangeCheck function?
If so, somebody let Oracle know so that they can sue the government.
5.56x45mm is the specifications for the NATO-standard small-arms ammunition, used by pretty much every modern military assault rifle that isn't a Kalashnikov derivative (and some that are), as well as some police sniper rifles and various civilian rifles.
And now I've explained the joke.
You mean like the one about TCP/IP via avian carriers?
it really is viral licensing now
---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
If the LZO folks had an easy way to purchase a license to their products (purchase online with credit card), they would have a little more money in their pockets.. Instead, they get a tiny bit of publicity.. and anyone who cares will simply use a free (as in MIT/BSD) library, such as FastLZ or LZJB, 7-Zip.
They just have to say, "OK. Sorry. We'll stop distributing it now." However the fact is that it continues to distribute itself.
the GPL makes allowances for things like plugins, extensions, addons, etc and since flame is clearly module based (as discovered by virus researchers) only the one module with the lzo stuff would have to be released under GPL.
Right, distributing is the key.
But that means we have to figure out who it was distributed to, and by whom. I think we can agree that the owners of the targeted Iranian computers were recipients of the distribution, so they get to request the source, right? (Ha!)
But what about anyone else? If the distribution to other people was not authorized the the original distributor (e.g. an Iranian infects Internet-connected computers after his air-gapped nuclear equipment controlling system was infected), I'm not sure they'd have the right to request the source. But I haven't read the GPL in quite some time.
Better ping; but more packet fragmentation.
I realize this is a bit of a tongue-in-cheek news item, but isn't government by definition above the law? I mean, if it actually got serious, wouldn't the president just pass an executive order making it exempt from copyright law?
In any case, the government isn't distributing it, it is self distributing! ;')
Assuming for a moment that Flame is a work by or created under contract for the USG:
Based on my laymen understanding of how a classified work is handled by the USG, if it marks a work with a security classification, said work is therefore condemned and solely owned by the USG, making all previous contracts and copyrights moot.
That's not to say that they would claim sole ownership and copyright of Lua and the other works used to create the final product, but rather just the final product. Therefore, no code release, and not even under the FOIA.
Luke, help me take this mask off
There is a commercial option, they just have to have licensed it from Oberhumer.
That might have been a fun discussion.
Assuming the US government is behind these masterpieces anyone who was given a binary by the US government can request the full source code.
If you happen to stumble upon the binary after passing through many middle-men the original author doesn't owe you anything.
5.56x45 is not the best option for physical layer, though - it has fragmentation issues.
Umm, no. If they have never intentionally released their product under a source code license such as the GPL, then asking them for the source code is silly. Repeat after me. A GPL violation does not force the company to release their code under the GPL. I am not a lawyer but I've spent a lot of time studying the GPL and how it works with copyright law.
A judge can and should punish them monetarily for existing distribution, and prevent further distribution of the product so long as a license compliance issue exists. This all said, I think users calling on companies to open their source because of a GPL violation, particularly when the product is a core proprietary product is harmful to the GPL specifically, and to open source in general. It perpetuates the lie I spoke of.
We should point out violations, however, and point companies at the remedies I listed. At least one of the remedies is required for further distribution, but any one will do.
Oh man, I can't WAIT to see what RMS has to say about "unintentinal forced distribution". If you give me the virus, I didn't ask for it and you (also being infected) didn't intend to give it to me. I wonder if we'll see a GPLv4 soon to cover this issue like GPLv3 covered Tivoisation!
Glad someone else noticed this. There is no mention of the US government, or any indication that the article author has any idea who wrote the code.
Has the US government really admitted to writing these viruses? Did I miss something?
the virus/worm authors who used GPLed code, only.
Why shall the government be assumed the obligation?
Read 'em and weep:
http://en.wikipedia.org/wiki/Sovereign_immunity#United_States
http://en.wikipedia.org/wiki/Eleventh_Amendment_to_the_United_States_Constitution
People should not fear their government. Governments should fear their people.