I was going to post the following on the linksys tinypeap forum. Comments? And/or we could submit a slashdot story. ==== Please don't use TinyPEAP. The authors have stolen code from the FreeRADIUS project (not the legal definition of "steal" since code isn't physical property, but theft all the same). TinyPEAP uses TLS (and possibly other) code from FreeRADIUS. FreeRADIUS is licensed under the GPL. That means if you take FreeRADIUS code and redistribute it, you must also distribute your modifications to the code. Or if you incorporate FreeRADIUS code into your own, you've "infected" your own code and must distribute the source. Many FreeRADIUS developers have worked hard to create the EAP functionality. Please don't step on their rights by using TinyPEAP. The TinyPEAP developers were contacted but did not respond. Next will be legal action. Frank Cusack FreeRADIUS developer ====
Frank Cusack <fcusack@fcusack.com> wrote:
I was going to post the following on the linksys tinypeap forum. Comments? And/or we could submit a slashdot story.
Comments below. Let's do some edits, and then go to slashdot, their forum, and gpl-violations.org.
==== Please don't use TinyPEAP. The authors have stolen code from the FreeRADIUS project (not the legal definition of "steal" since code isn't physical property, but theft all the same).
I wouldn't go quite that far. I would say: --- TinyPEAP is using code taken from FreeRADIUS.[ref-proof] They have removed the authors copyrights, and are releasing the code under terms incompatible with the GPL.[ref-license] We have contacted the tinyPEAP developers, and have yet to receive a response. Until this issue is sorted out, we ask that people be aware that by using tinyPEAP you may be contributing to copyright infringement and GPL violation, and may become involved in any legal action resulting from this issue. We have asked the authors to correct this problem by either: 1) re-writing tinyPEAP to remove the infringing code or 2) releasing the source code for tinyPEAP under terms of the GPL. If the problem is not corrected, or if we do not receive a response from the tinyPEAP developers, we will be forced to proceed to the next step. Frank Cusack FreeRADIUS Server Project http://www.freeradius.org
I like that version much better. More diplomatic, but gets the point and seriousness across. --Mike Alan DeKok wrote:
Frank Cusack <fcusack@fcusack.com> wrote:
I was going to post the following on the linksys tinypeap forum. Comments? And/or we could submit a slashdot story.
Comments below. Let's do some edits, and then go to slashdot, their forum, and gpl-violations.org.
==== Please don't use TinyPEAP. The authors have stolen code from the FreeRADIUS project (not the legal definition of "steal" since code isn't physical property, but theft all the same).
I wouldn't go quite that far. I would say:
--- TinyPEAP is using code taken from FreeRADIUS.[ref-proof] They have removed the authors copyrights, and are releasing the code under terms incompatible with the GPL.[ref-license]
We have contacted the tinyPEAP developers, and have yet to receive a response. Until this issue is sorted out, we ask that people be aware that by using tinyPEAP you may be contributing to copyright infringement and GPL violation, and may become involved in any legal action resulting from this issue.
We have asked the authors to correct this problem by either:
1) re-writing tinyPEAP to remove the infringing code
or
2) releasing the source code for tinyPEAP under terms of the GPL.
If the problem is not corrected, or if we do not receive a response from the tinyPEAP developers, we will be forced to proceed to the next step.
Frank Cusack FreeRADIUS Server Project http://www.freeradius.org - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html
participants (3)
-
Alan DeKok -
Frank Cusack -
Michael Griego