If the copyright-holder of the GPL'd work doesn't do anything, the consequences are... nothing.
The owners of lots of GPL'd works such as the GNU project tend to take an approach of quiet negotiation. They will contact the violators and attempt to inform them about their responsibilities when distributing GPL'd software. They want software to be free for examination and modification and many violations are unintentional.
GPL violations are extremely common, especially with Linux. For example every ip surveillance camera runs Linux/Busybox/etc and I have never seen one that provides source.
I believe your last statement is incorrect. Applications written entirely by your developers that merely happen to run on a Linux-based operating system, distributed in conjunction with those works (Linux/Busybox/etc), are separate works within the meaning of copyright law. GPL requires you to provide complete and corresponding source for the GPL’d components and your modifications thereto, but not for independent proprietary applications.
For example, programs compiled by gcc (GPL) are not considered derived works and therefore don't need to also hold the GPL license.
In the case of the topic, that appears to be a violation as the game can be considered a derived work. Most violations are handled on a case by case basis if there is legal action due to the nature of "derived work".
If you distribute binary GPL'd software such as the Linux kernel you also have to provide the exact source used to generate those binaries.
Because ip cameras are shipped with binary Linux kernel images they should also provide either the exact source used or an offer of how to get the source.
> For example, programs compiled by gcc (GPL) are not considered derived works
Yep you're right. We probably just misunderstood each other. I was specifically referring to GPL'd components like Linux & Busybox, not any applications that happen to be running on top of them.
I'm bad at open source licenses, but wouldn't they need to make modifications to the Linux they're running on to be required to distribute their source?
Because they are distributing GPL'd software they also have to at least offer the exact source they used. If they are using an unmodified kernel, giving users a link to a git tag would satisfy this.
In practice, every embedded use of Linux I've seen has included at least some modifications.
Cynically, I would guess just about nothing. If it could be proved that the GPL'd source was compiled in the real game, and was knowingly taken from a GPL'd source, I suppose whoever holds the rights could sue. I think it'd be difficult to prove sufficiently.
It depends on if and who pursues the violation. For example, apple is violating the GPL with bash by distributing a binary but not distributing all the source code used to compile it.
I believe there are also violations by vmware and lots of others (I believe ubiquiti?)
That said, there are legitimate ways to distribute GPL code, such as a dual license.
You could write code and license it to company A under one license, and release it under GPL to company B.
company A could have any rights or responsibilities you grant, while company B would have to comply with the distribution restrictions of the GPL.
It's also worth noting that the GPL does not restrict how anyone USES the software, it only restricts how the software is redistributed.
If the copyright-holder of the GPL'd work doesn't do anything, the consequences are... nothing.
The owners of lots of GPL'd works such as the GNU project tend to take an approach of quiet negotiation. They will contact the violators and attempt to inform them about their responsibilities when distributing GPL'd software. They want software to be free for examination and modification and many violations are unintentional.
GPL violations are extremely common, especially with Linux. For example every ip surveillance camera runs Linux/Busybox/etc and I have never seen one that provides source.
I believe your last statement is incorrect. Applications written entirely by your developers that merely happen to run on a Linux-based operating system, distributed in conjunction with those works (Linux/Busybox/etc), are separate works within the meaning of copyright law. GPL requires you to provide complete and corresponding source for the GPL’d components and your modifications thereto, but not for independent proprietary applications.
For example, programs compiled by gcc (GPL) are not considered derived works and therefore don't need to also hold the GPL license.
In the case of the topic, that appears to be a violation as the game can be considered a derived work. Most violations are handled on a case by case basis if there is legal action due to the nature of "derived work".
> I believe your last statement is incorrect.
If you distribute binary GPL'd software such as the Linux kernel you also have to provide the exact source used to generate those binaries.
Because ip cameras are shipped with binary Linux kernel images they should also provide either the exact source used or an offer of how to get the source.
> For example, programs compiled by gcc (GPL) are not considered derived works
Yep you're right. We probably just misunderstood each other. I was specifically referring to GPL'd components like Linux & Busybox, not any applications that happen to be running on top of them.
10 replies →
I'm bad at open source licenses, but wouldn't they need to make modifications to the Linux they're running on to be required to distribute their source?
Because they are distributing GPL'd software they also have to at least offer the exact source they used. If they are using an unmodified kernel, giving users a link to a git tag would satisfy this.
In practice, every embedded use of Linux I've seen has included at least some modifications.
No, the whole binary this code was compiled into needs to be GPL licensed in its entirety.
https://en.wikipedia.org/wiki/BusyBox#GPL_lawsuits
The author can sue for damages and receive cash.
Cynically, I would guess just about nothing. If it could be proved that the GPL'd source was compiled in the real game, and was knowingly taken from a GPL'd source, I suppose whoever holds the rights could sue. I think it'd be difficult to prove sufficiently.
It depends on if and who pursues the violation. For example, apple is violating the GPL with bash by distributing a binary but not distributing all the source code used to compile it.
I believe there are also violations by vmware and lots of others (I believe ubiquiti?)
That said, there are legitimate ways to distribute GPL code, such as a dual license.
You could write code and license it to company A under one license, and release it under GPL to company B.
company A could have any rights or responsibilities you grant, while company B would have to comply with the distribution restrictions of the GPL.
It's also worth noting that the GPL does not restrict how anyone USES the software, it only restricts how the software is redistributed.
> For example, apple is violating the GPL with bash by distributing a binary but not distributing all the source code used to compile it.
https://opensource.apple.com/source/bash/bash-106.220.2/
rootless.h
1 reply →