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.
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.
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.'"
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.
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.
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).
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.
Better ping; but more packet fragmentation.